I am experiencing an issue with HTTPS proxy authentication using the wget2(version 2.2.0) command. While HTTP proxy authentication and unauthenticated HTTPS proxy connections are working as expected, authentication is failing specifically for HTTPS proxy. setup details and commands: Linux host ---- Linux PC(squid proxy web server)----- remote server # wget2 --debug --max-threads=1 --http-proxy-user="test" --http-proxy-password="\*\*\*\*\*\*\*\*\*" --https-proxy=[http://10.10.10.10:1](http://10.10.10.10:1) --no-check-certificate [https://20.20.20.1/./script](https://20.20.20.1/./script) -O backup 21.135227.254 Local URI encoding = 'ANSI_X3.4-1968' 21.135227.254 Input URI encoding = 'ANSI_X3.4-1968' 21.135227.254 Fetched HSTS data from '/.local/share/wget/.wget-hsts' 21.135227.254 Fetched HPKP data from '/.local/share/wget/.wget-hpkp' 21.135227.254 set_exit_status(0) 21.135227.254 path ./script -\> 21.135227.254 script 21.135227.254 host_add_job: job fname (null) 21.135227.254 host_add_job: 0x7088e0 [https://20.20.20.1/./script](https://20.20.20.1/./script) 21.135227.254 host_add_job: qsize 1 host-qsize=1 21.135227.254 queue_size: qsize=1 21.135227.254 queue_size: qsize=1 21.135227.255 \[0\] action=1 pending=0 host=0x0 goaway=n/a 21.135227.255 dequeue job [https://20.20.20.1/./script](https://20.20.20.1/./script) 21.135227.255 resolving 10.10.10.10:1... 21.135227.255 has 10.10.10.10:1 21.135227.255 has 10.10.10.10:1 21.135227.255 trying 10.10.10.10:1... Proxy connection failed with: HTTP/1.1 407 Proxy Authentication Required Server: squid/4.10 Mime-Version: 1.0 Date: Wed, 21 Jan 2026 11:22:37 GMT Content-Type: text/html;charset=utf-8 Content-Length: 3441 X-Squid-Error: ERR_CACHE_ACCESS_DENIED 0 Vary: Accept-Language Content-Language: en Proxy-Authenticate: Basic realm="proxy" X-Cache: MISS from localhost X-Cache-Lookup: NONE from localhost:1 Via: 1.1 localhost (squid/4.10) Connection: keep-alive ERROR: Cache Access Denied \<!-- /\* \* Copyright (C) 1996-2020 The Squid Software Foundation and contributors \* \* Squid software is distributed under GPLv2+ license and includes \* contributions from numerous individuals and organizations. \* Please see the COPYING an 21.135227.257 closing connection Failed to connect: Connect error 21.135227.257 host_final_failure: qsize=0 21.135227.257 set_exit_status(4) 21.135227.257 host_increase_failure: 20.20.20.1 failures=1 21.135227.257 \[0\] action=3 pending=1 host=0x708440 goaway=n/a 21.135227.257 released job https://20.20.20.1/./script 21.135227.257 \[0\] action=1 pending=0 host=0x0 goaway=n/a 21.135227.257 host 20.20.20.1 is blocked (qsize=1) 21.135227.257 main: wake up 21.135227.257 main: done 21.135227.258 blacklist [https://20.20.20.1/./script](https://20.20.20.1/./script) WIth wget command, working as expected # wget --debug -e https-proxy=[http://test:\*\*\*\*\*\*\*\*\*@10.10.10.10:1](http://test:*********@10.10.10.10:1) --no-check-certificate [https://20.20.20.1/./script](https://20.20.20.1/./script) -O backup Setting https-proxy (httpsproxy) to [http://test:\*\*\*\*\*\*\*\*\*@10.10.10.10:1](http://test:*********@10.10.10.10:1) Setting https-proxy (httpsproxy) to [http://test:\*\*\*\*\*\*\*\*\*@10.10.10.10:1](http://test:*********@10.10.10.10:1) Setting --check-certificate (checkcertificate) to 0 Setting --check-certificate (checkcertificate) to 0 Setting --output-document (outputdocument) to backup Setting --output-document (outputdocument) to backup DEBUG output created by Wget 1.20.3 on linux-gnu. Reading HSTS entries from /.wget-hsts --2026-01-21 13:52:44-- [https://20.20.20.1/script](https://20.20.20.1/script) Connecting to 10.10.10.10:1... connected. Created socket 81. Releasing 0x0000000000d0bba0 (new refcount 0). Deleting unused 0x0000000000d0bba0. \---request begin--- CONNECT 20.20.20.1:443 HTTP/1.1 User-Agent: Wget/1.20.3 (linux-gnu) Proxy-Authorization: Basic dGVzdF9xYTpicm9hZGNvbQ== Host: 20.20.20.1:443 \---request end--- proxy responded with: \[HTTP/1.1 200 Connection established \] Initiating SSL handshake. Handshake successful; connected socket 81 to SSL handle 0x0000000000d0ca30 certificate: subject: O=Internet Widgits Pty Ltd,ST=Some-State,C=AU issuer: O=Internet Widgits Pty Ltd,ST=Some-State,C=AU WARNING: cannot verify 20.20.20.1's certificate, issued by 'O=Internet Widgits Pty Ltd,ST=Some-State,C=AU': Self-signed certificate encountered. WARNING: certificate common name '' doesn't match requested host name '20.20.20.1'. \---request begin--- GET /script HTTP/1.1 User-Agent: Wget/1.20.3 (linux-gnu) Accept: _/_ Accept-Encoding: identity Host: 20.20.20.1 Connection: Keep-Alive Proxy-Connection: Keep-Alive \---request end--- Proxy request sent, awaiting response... ---response begin--- HTTP/1.1 200 OK Date: Wed, 21 Jan 2026 11:20:33 GMT Server: Apache/2.4.41 (Ubuntu) Last-Modified: Wed, 06 Aug 2025 06:07:34 GMT ETag: "3582560-63bac28265156" Accept-Ranges: bytes Content-Length: 56108384 Keep-Alive: timeout=5, max=100 Connection: Keep-Alive \---response end--- 200 OK Registered socket 81 for persistent reuse. Length: 56108384 (54M) Saving to: 'backup' backu 100%\[===================\>\] 53.51M 13.6MB/s in 3.9s 2026-01-21 13:52:48 (13.6 MB/s) - 'backup' saved \[56108384/56108384\] # Hi,\ \ \ iirc, there are different types of https proxies, acting differently.\ Pretty sure that wget2 doesn't work out of the box for all types.\ What could be helpful:\ - open an issue at [https://gitlab.com/gnuwget/wge<wbr>t2/issues](https://gitlab.com/gnuwget/wget2/issues)\ - use '--debug --max-threads=1\` with your failing command and add the\ output to the issue (make sure to remove credentials and any information\ that should not be public)\ - does it work with wget 1.x ? (if yes, also provide output from --debug)\ - can you provide a recipe for reproduction? e.g., one python script\ acting as the proxy, another one as the server\ \ Regards, Tim\ \ On 1/20/26 8:26 AM, Samiya Khanum via Primary discussion list for GNU\ Wget wrote:\ \> Hi,\ \>\ \> I am experiencing an issue with HTTPS proxy authentication using the\ \> wget2(version\ \> 2.2.0) command. While HTTP proxy authentication and unauthenticated HTTPS\ \> proxy connections are working as expected, authentication is failing\ \> specifically for HTTPS.\ \>\ \> Could you please review the command options I am using below and let me\ \> know if they are correct, or if this is a known issue?\ \>