[Lynx-dev] [Minor bug] Lynx does not convert relative URI references starting with a colon, correctly

[Mathieu Bonnet]

AS: Thanks to CC me any reply, as I am not subscribed to this list.


Hi,

Lynx does not convert relative URI references starting with a colon, 
correctly. If I have a relative URI reference, in HTML, like `<a 
href=":foo">foo</a>`, then Lynx will handle it as the absolute URI 
`:foo` (which is not even a correct absolute URI, as the scheme part 
cannot be empty (and Lynx does tell me, if I try to activate it: "Badly 
formed address :foo")).

As per RFC 1808 §2.4.2 (http://www.faqs.org/rfcs/rfc1808.html), Lynx 
should handle this URI reference as a relative URI path (i.e., if the 
base URI was "http://example.com/news/latest";, then the final absolute 
URI would be "http://example.com/news/:foo";), because the colon is not 
located "after the first character" (it *is* the first character).


Thanks to anyone who will take the time to correct this behaviour.


Bye.


-- 
Mathieu Bonnet <address@hidden>

pgpErsDAQwYHO.pgp
Description: PGP signature