Follow-up Comment #1, bug #68250 (group wget): Wget doesn’t actually use the proxy URL scheme for anything because it only supports HTTP. There is a diagnostic for other URL schemes, but it is [https://cgit.git.savannah.gnu.org/cgit/wget.git/tree/src/retr.c?id=e514d54dfc540644f33c32ed96dc29f0cf0984a3#n936 suppressed] when the scheme is the same as the one the proxy is _for_. Unfortunately, this means changing https:// to mean [https://www.chromium.org/developers/design-documents/secure-web-proxy/ Secure Web Proxy] would be a breaking change; someone might have https_proxy=https://$PROXY in a script without realizing how this is redundant. An alternative would be a flag like --proxy-secure-protocol, akin to --proxy-user. That would in principle allow running SOCKS over TLS too, in the future.
As a stopgap solution, you can run netcat in listening mode to spawn a TLS
client, for example:
ncat -lkc 'gnutls-cli --logfile=/dev/stderr proxy' 8080
And set https_proxy=localhost:8080.
_______________________________________________________
Reply to this item at:
<https://savannah.gnu.org/bugs/?68250>
_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/
signature.asc
Description: PGP signature
