On 2002-03-05 11:41 +0100, Philipp Thomas wrote:
> When requesting a URL like http://tmp.logix.cz/slash.xp//// , wget shortens
> this to http://tmp.logix.cz/slash.xp/. All Browsers I tested (Opera 6b1,
> Mozilla 0.9.8, Konqueror 2.9.2) pass this URL as given.
>
> So the question is, why wget (1.8.1) does what it does
Presumably because the author thought that both URLs are
equivalent. To my surprise, RFC 1945 seems to agree with you. It
says :
URI = ( absoluteURI | relativeURI ) [ "#" fragment ]
absoluteURI = scheme ":" *( uchar | reserved )
relativeURI = net_path | abs_path | rel_path
net_path = "//" net_loc [ abs_path ]
abs_path = "/" rel_path
rel_path = [ path ] [ ";" params ] [ "?" query ]
path = fsegment *( "/" segment )
fsegment = 1*pchar
segment = *pchar
Which I understand to mean that a segment can be empty, which
in turn could be interpreted as stating that the trailing
slashes in slash.xp//// are significant.
That said, setting up a web site to rely on empty path segments
strikes me as a creative way of looking for problems. :-) Why is
it important to you ?
--
André Majorel <URL:http://www.teaser.fr/~amajorel/>
std::disclaimer ("Not speaking for my employer");
