GNU bug report logs -
#8622
24.0.50; url-parse does not implement RFC3986 5.2
Previous Next
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
View this message in rfc822 format
Julien Danjou <julien <at> danjou.info> writes:
>> Julien Danjou <julien <at> danjou.info> writes:
>>
>>> URL listed in 5.4.1 and 5.4.2 does not work such as:
>>>
>>> "../../../g" = "http://a/g"
>>
>> Where does the "a" come from?
>
> Read:
>
> "http://a/../../../g" = "http://a/g"
5.2 talks about relative URLs, though, so "http://a/../../../g" seems
irrelevant...
5.4.1 also talks about relative URLs, and how to resolve them if you
have a base address. But `url-generic-parse-url' does not, as far as I
can tell, deal with the concept of "relative URLs and bases", but only
parses full, non-relative URLs.
And for a full URL, this looks correct to me:
(url-generic-parse-url "http://a/../../../g")
=>
[cl-struct-url "http" nil nil "a" 80 "/../../../g" nil nil t nil]
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog http://lars.ingebrigtsen.no/
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.