unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Julien Danjou <julien@danjou.info>
To: Lars Magne Ingebrigtsen <larsi@gnus.org>
Cc: Andreas Schwab <schwab@linux-m68k.org>, 8622@debbugs.gnu.org
Subject: bug#8622: 24.0.50; url-parse does not implement RFC3986 5.2
Date: Sun, 11 Sep 2011 18:26:35 +0200	[thread overview]
Message-ID: <87y5xv3v0k.fsf@keller.adm.naquadah.org> (raw)
In-Reply-To: <m3vcsznjag.fsf@stories.gnus.org> (Lars Magne Ingebrigtsen's message of "Sun, 11 Sep 2011 18:19:35 +0200")

[-- Attachment #1: Type: text/plain, Size: 954 bytes --]

On Sun, Sep 11 2011, Lars Magne Ingebrigtsen wrote:

> Julien Danjou <julien@danjou.info> writes:
>
>> It seems to me that it's what 5.4 talks about.
>
> This is how 5.4 starts:
>
> 5.4.  Reference Resolution Examples
>
>    Within a representation with a well defined base URI of
>
>       http://a/b/c/d;p?q
>
>    a relative reference is transformed to its target URI as follows.

Then go to 5.4.2:

   Although the following abnormal examples are unlikely to occur in
   normal practice, all URI parsers should be capable of resolving them
   consistently.  Each example uses the same base as that above.

   Parsers must be careful in handling cases where there are more ".."
   segments in a relative-path reference than there are hierarchical
   levels in the base URI's path.  Note that the ".." syntax cannot be
   used to change the authority component of a URI.


-- 
Julien Danjou
❱ http://julien.danjou.info

[-- Attachment #2: Type: application/pgp-signature, Size: 835 bytes --]

  reply	other threads:[~2011-09-11 16:26 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-05 16:14 bug#8622: 24.0.50; url-parse does not implement RFC3986 5.2 Julien Danjou
2011-09-11  4:36 ` Lars Magne Ingebrigtsen
2011-09-11 12:03   ` Julien Danjou
2011-09-11 14:00     ` Andreas Schwab
2011-09-11 14:39       ` Julien Danjou
2011-09-11 15:21         ` Andreas Schwab
2011-09-11 15:26           ` Julien Danjou
2011-09-11 15:46             ` Andreas Schwab
2011-09-11 15:53               ` Julien Danjou
2011-09-11 16:04                 ` Lars Magne Ingebrigtsen
2011-09-11 16:15                   ` Julien Danjou
2011-09-11 16:19                     ` Lars Magne Ingebrigtsen
2011-09-11 16:26                       ` Julien Danjou [this message]
2011-09-11 16:30                         ` Lars Magne Ingebrigtsen
2011-09-11 16:39                           ` Julien Danjou
2011-09-11 16:37                             ` Lars Magne Ingebrigtsen
2011-09-11 16:47                               ` Julien Danjou
2011-09-11 16:34                         ` Lars Magne Ingebrigtsen
2015-12-25 22:05                           ` Lars Ingebrigtsen
2018-04-15 20:14                           ` Lars Ingebrigtsen
2011-09-11 18:53                         ` Lars Magne Ingebrigtsen
2011-09-11 16:09                 ` Andreas Schwab
2011-09-11 15:20     ` Lars Magne Ingebrigtsen

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87y5xv3v0k.fsf@keller.adm.naquadah.org \
    --to=julien@danjou.info \
    --cc=8622@debbugs.gnu.org \
    --cc=larsi@gnus.org \
    --cc=schwab@linux-m68k.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).