[bug #68250] wget doesn't honor TLS URL in http_proxy

--8323329-1714636915-1777427101=:189821
Content-Type: TEXT/plain; CHARSET=utf-8
Content-Transfer-Encoding: QUOTED-PRINTABLE
Content-Disposition: inline

Follow-up Comment #1, bug #68250 (group wget):=0A=0AWget doesn=E2=80=99t ac=
tually use the proxy URL scheme for anything because it only=0Asupports HTT=
P.  There is a diagnostic for other URL schemes, but it is=0A[https://cgit.=
git.savannah.gnu.org/cgit/wget.git/tree/src/retr.c?id=3De514d54dfc540644f33=
c32ed96dc29f0cf0984a3#n936=0Asuppressed] when the scheme is the same as the=
 one the proxy is _for_.=0AUnfortunately, this means changing https:// to m=
ean=0A[https://www.chromium.org/developers/design-documents/secure-web-prox=
y/ Secure=0AWeb Proxy] would be a breaking change;  someone might have=0Aht=
tps_proxy=3Dhttps://$PROXY in a script without realizing how this is=0Aredu=
ndant.  An alternative would be a flag like --proxy-secure-protocol, akin=
=0Ato --proxy-user.  That would in principle allow running SOCKS over TLS t=
oo, in=0Athe future.=0A=0AAs a stopgap solution, you can run netcat in list=
ening mode to spawn a TLS=0Aclient, for example:=0A=0Ancat -lkc 'gnutls-cli=
 --logfile=3D/dev/stderr proxy' 8080=0A=0AAnd set https_proxy=3Dlocalhost:8=
080.=0A=0A=0A    _______________________________________________________=0A=
=0AReply to this item at:=0A=0A  <https://savannah.gnu.org/bugs/?68250>=0A=
=0A_______________________________________________=0AMessage sent via Savan=
nah=0Ahttps://savannah.gnu.org/=0A
--8323329-1714636915-1777427101=:189821
Content-Type: APPLICATION/pgp-signature; name=signature.asc

-----BEGIN PGP SIGNATURE-----

iHUEABYIAB0WIQQk97aszIMMAvLLwm6qLAuaBUf3TgUCafFinQAKCRCqLAuaBUf3
TtT/AP4rHHo1uV9S8ZveIGGIyGzxEFb+bIE8LfWMzV+pXaGe9gEAvCvBQ1c/nGVu
5iYbL2ecyCcpdEhDcDOTj6YU3yFxbQ8=
=6iRh
-----END PGP SIGNATURE-----

--8323329-1714636915-1777427101=:189821--