Frank McCown <[EMAIL PROTECTED]> writes: > Earlier today I sent an email explaining that wget already handles > ".." in the middle of a URL correctly, it just doesn't handle ".." > immediately after the domain name correctly.
But it does, at least according to rfc1808, which mandates leading ".." to be left alone. I don't know what the new rfc3986 says about that, though. > Wget will currently convert the request of > http://foo.org/BLAH/../page.html to http://foo.org/page.html. What > it should also do is convert a request for > http://foo.org/../page.html to http://foo.org/page.html. Not according to rfc1808. > As far as I can tell, the only time you'd want to encode ".." to > "%2E%2E" would be in a query string. Are you referring to URL encoding or to file name encoding? As far as I know, Wget converts ".." to "%2E%2E" only when doing file name encoding, to make sure that malformed or malicious URLs don't write to arbitrary portions of the file system.
