According to the wget release notes for 1.10 "*** Talking to SSL/TLS servers over proxies now actually works. Previous versions of Wget erroneously sent GET requests for https URLs. Wget 1.10 utilizes the CONNECT method designed for this purpose."
However, I have tried versions 1.10, 1.10.1, and 1.10.2, and they all appear to do the same thing- attempt to connect directly to the server (at port 443) instead of going through the proxy. Here is what I see 1) HTTP server, no proxy - works fine 2) HTTPS server, no proxy - works fine 3) HTTP server, proxy - works fine 4) HTTPS server, proxy - does not work Here is debug output ---------------------------------------------------- C:\GnuWin32\GETGNU~1>bin\wget -v -d --no-check-certificate https://secure.mvnt4.com/tcf/OnlineBanking/index.jsp Setting --check-certificate (checkcertificate) to 0 DEBUG output created by Wget 1.10.2 on Windows. --11:46:09-- https://secure.mvnt4.com/tcf/OnlineBanking/index.jsp => `index.jsp' Resolving secure.mvnt4.com... seconds 0.00, 207.250.12.106 Caching secure.mvnt4.com => 207.250.12.106 Connecting to secure.mvnt4.com|207.250.12.106|:443... seconds 0.00, Closed fd 736 failed: Connection timed out. Releasing 0x008a5308 (new refcount 1). Retrying. ---------------------------------------------------------------- Whereas if I connect to an HTTP URL, everything else the same, wget is able to retrieve the page and it reports ------------------------------------------------------------------------ --------------- Resolving <PROXYADDRESS DELETED>... seconds 0.00, 157.127.124.141 Caching <PROXYADDRESS DELETED> => 157.127.124.141 Connecting to <PROXYADDRESS DELETED>|157.127.124.141|:80... seconds 0.00, connected. Created socket 752. Releasing 0x008a53d0 (new refcount 1). ---request begin--- etc. ------------------------------------------------------------------------ -------------- Is WGET expecting an HTTPS proxy address for accessing HTTPS websites? That is not correct behavior... In other words, it appears that the fix reported in the 1.10 release did not take. Any suggestions? Thanks very much and down with all HTTP proxies!! Jim Schatzman