-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Richard wrote: > Hi Micah, > > I've tried to post this reply to the mailing list but it's getting > blocked by SpamAssassin so having to reply directly - hope that's OK.
Sure; it's probably due to the "xxx" strings within URLs. :) I was thinking perhaps the "working" case with Wget 1.11 would be using a so-called "FTP proxy"; an FTP server that proxies to other servers. Of course, the FTP-handling logic for FTP-over-HTTP proxies is entirely handled by the HTTP proxy server, so it makes sense that it would work there. The logs look like enough to fish out the problem, so I'll do some snooping around to see what can be done about this. Judging from this bit from the failing Wget 1.11 logs: - --2008-03-10 18:59:10-- ftp://ftp.xxxxxxx.pwp.blueyonder.co.uk/logs/access.20080309.gz Host `ftp.xxxxxxx.pwp.blueyonder.co.uk' has not issued a general basic challenge. Resolving webcache.virginmedia.com... 195.188.152.6 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. - -- 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 iD8DBQFH1Y8t7M8hyUobTrERAietAJ4pzcZ9vVOTk4Bsy9wn89J5oHCyTQCdEgbR VtaAtKiIhh1lXmTi9CAB9do= =vfM1 -----END PGP SIGNATURE-----
