GNU bug report logs - #8622
24.0.50; url-parse does not implement RFC3986 5.2

Previous Next

Package: emacs;

Reported by: Julien Danjou <julien <at> danjou.info>

Date: Thu, 5 May 2011 16:15:02 UTC

Severity: normal

Tags: fixed

Found in version 24.0.50

Done: Lars Ingebrigtsen <larsi <at> gnus.org>

Bug is archived. No further changes may be made.

Full log


Message #62 received at 8622 <at> debbugs.gnu.org (full text, mbox):

From: Julien Danjou <julien <at> danjou.info>
To: Lars Magne Ingebrigtsen <larsi <at> gnus.org>
Cc: 8622 <at> debbugs.gnu.org, Andreas Schwab <schwab <at> linux-m68k.org>
Subject: Re: bug#8622: 24.0.50; url-parse does not implement RFC3986 5.2
Date: Sun, 11 Sep 2011 18:47:34 +0200
[Message part 1 (text/plain, inline)]
On Sun, Sep 11 2011, Lars Magne Ingebrigtsen wrote:

> Julien Danjou <julien <at> danjou.info> writes:
>
>> I'm sorry, I am missing why this does not apply to the example I gave.
>
> http://a/../../b is not a relative URL.  :-)
>
> The entire thing is about how to glue a base URL, like "http://a/b/c"
> together with a relative URL, like "../../d".  If you're not gluing URLs
> together, then the section does not apply.  At all.

Oh ok. But if you consider the base URL being http://a/, you clearly
match this case. I admit we are not doing relative anyhow, but I don't
think absolute and relative are supposed to have different behaviour in
such a case.

And it seems that 5.2.4 clearly explains the algo in our (absolute) case,
don't you think?


-- 
Julien Danjou
❱ http://julien.danjou.info
[Message part 2 (application/pgp-signature, inline)]

This bug report was last modified 7 years and 122 days ago.

Previous Next


GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.