-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Micah Cowan wrote:
> it looks to me like your URL > (ftp://ftp.xxxxxxx.pwp.blueyonder.co.uk/../logs/access.20080309) is > being transmuted by some URL "cleanup" code well before it ever gets to > the FTP handle. My guess is that this change was intentionally done, as > such a URL for HTTP would probably be wrong (I'm not sure that it's > actually ill-formed; but for safety reasons it was probably a good idea > to remove ".." from the beginning of paths in HTTP). However, it's > perfectly fine for FTP URLs, and removing it for them is misbehavior. This change was introduced in 2006 Feb, at the suggestion of Frank McCown: http://article.gmane.org/gmane.comp.web.wget.general/5290/ The change can be seen here: http://hg.addictivecode.org/wget/mainline/rev/798506c1ce67/ The change was introduced to comply with the recommended algorithm for normalizing paths in RFC 3986 (section 5.2.4). So the change was deliberate, and done to comply with recommended practice. The thing is, of course, is that it sort of breaks the FTP scheme defined in RFC 1738. Are there any updates to the FTP URL definition? I don't see any (it seems to me that the RFC index would show an "Updated-By" for 1738 to FTP URL updates, as it does for gopher and mailto). I'm going to punt this so it doesn't hold up 1.11.1 (speaking of which, has anyone been banging on the prerelease? :\ ). I vote that we ignore what 3986 says with respect to ftp paths, perhaps passing a flag to the path_simplify function so it knows whether to do that or not? - -- Micah J. Cowan Programmer, musician, typesetting enthusiast, gamer... http://micah.cowan.name/ -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFH4aoa7M8hyUobTrERAnh2AJ9TBQwyknhPl9pUFzVuTnk9LtQ0rQCcCTO0 VNz+Bv6tVv6KvSl19yIVeBs= =nRHg -----END PGP SIGNATURE-----
