-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I could've sworn I sent my response to this, to the list, but I must have accidentally hit "Reply" instead of "Reply All".
Slava Grig wrote: > Hello! > > I try to set environment variable https_proxy and download something through > > wget --no-check-certificate https://_something_.com/_some_file_ > > but can't. Wget does not initiate a ssl connection to the proxy but > instead connects directly to the target host. This bit was wrong. I asked for --debug information to be sent privately (just in case) and explained how to ensure that his password doesn't show up Base64'd in the Authorization headers and what not. 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. Julien, I've CC'd you, in case you think this might be something you'd want to add to your GSoC proposal. If it _is_, it's probably something that should be done before the rest, so I can backport it into the 1.11 branch for a 1.11.2 release (since this is an important regression), rather than make people wait for 1.12 to come out (which is where I expect the rest of the authorization improvements would go). - -- Micah J. Cowan Programmer, musician, typesetting enthusiast, gamer, and GNU Wget Project Maintainer. http://micah.cowan.name/ -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFH86zl7M8hyUobTrERAvhoAJ0UY8cu9OtvVwIG7XDxCm0RPdfFZgCfVvSt NEeHVBhey76f2KdewsZAdds= =8ZUM -----END PGP SIGNATURE-----
