-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Micah Cowan wrote: > The log shows that: > > 1. Wget still doesn't wait for the Proxy to ask for authentication, > before sending Proxy-Authorization headers with its first request. > 2. Apparently, when going through a proxy, Wget now correctly waits to > receive a challenge from the destination server (as I intended), but > then _doesn't_ respond to the challenge with an Authorization header, > instead just treating the (first) 401 as a final header.
Slava, could you perhaps download and install Wget 1.11.1, and try it with the --auth-no-challenge option? That was added to support a case when there was a genuine need for Wget's older, less secure authentication behavior; it's intended to disable the new behavior. It may or may not fix your problem, and I'd be interested to know which it is. :) - -- Micah J. Cowan Programmer, musician, typesetting enthusiast, gamer, and GNU Wget Project Maintainer. http://micah.cowan.name/ -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFH9QzK7M8hyUobTrERAuOUAJ4ygaAyhihkeM/tG0j7hMexnHJZwwCeKhzi r3OHfZk8bDZu0DnQljyP7vU= =6i/0 -----END PGP SIGNATURE-----
