Re: wget fails using proxy with https-protocol
-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-
Re: wget fails using proxy with https-protocol
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Micah Cowan wrote: 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). Er, on reflection, that's a terrible idea, given that coding for GSoC doesn't even start until nearly June, and this is a serious regression that should be fixed as soon as it can be got to. Still, if you'd like to tackle it out-of-band, that'd be handy. :) - -- 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 iD8DBQFH87mY7M8hyUobTrERAuyjAJ0XJ8ImAFZ/J49EGQlc+HWWNdxhQACgiK3U bgyhQErH//V6bDkaeE9mLYM= =3fn1 -END PGP SIGNATURE-
wget fails using proxy with https-protocol
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. I found this problem in the wget 1.11, but version 1.10.2 work correctly. I use it on a Windows XP. wget was compiled from sources using Microsoft Visual Studio 2003.NET. Console output (ip-addresses are changed): wget.exe --no-check-certificate https://_something_.com/_some_file_ --2008-04-01 11:44:37-- https://_something_.com/_some_file_ Resolving _my_._proxy_.com... 10.XX.XX.XX Connecting to _my_._proxy_.com|10.XX.XX.XX|:3128... connected. WARNING: cannot verify _something_'s certificate, issued by `XXX': Self-signed certificate encountered. Proxy request sent, awaiting response... 401 Unauthorized Resolving _something_.com... 202.108.XXX.XXX Connecting to _something_.com|202.108.XXX.XXX|:443... failed: Socket is not c onnected. Retrying. Good by.
