Package: golang-go Version: 2:1.15~1 Followup-For: Bug #1026922 X-Debbugs-Cc: debbug.1026...@sideload.33mail.com
HD> I’d suppose there is a misunderstanding: HTTP_PROXY is used to HD> specify the proxy options of all HTTP connections, and HTTPS_PROXY HD> is used by HTTPS connections. Only in this way the names of HD> ALL_PROXY and NO_PROXY could make sense. What you describe is how the HTTP*_PROXY variables *should* work. But that’s not the case. For example, users of the Hydroxide app (written in Go) are being told to run: HTTPS_PROXY='socks5://127.0.0.1:9050' hydroxide $args See the problem? SOCKS has nothing to do with HTTP(S). SOCKS proxies cannot serve as an HTTP proxy because HTTP proxies are protocol-specific. A SOCKS proxy is protocol independant.
