Bug#1026922: golang-go: how HTTP*_PROXY should work v.s. how it operates currently

2023-02-03 Thread debbug . 1026922
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. Onl

Bug#1026922:

2023-02-03 Thread Huang Dawei
I’d suppose there is a misunderstanding: HTTP_PROXY is used to specify the proxy options of all HTTP connections, and HTTPS_PROXY is used by HTTPS connections. Only in this way the names of ALL_PROXY and NO_PROXY could make sense. --- Dawei Huang

Bug#1026922: golang-go: more action needed

2023-02-03 Thread debbug . 1026922
Package: golang-go Version: 2:1.15~1 Followup-For: Bug #1026922 X-Debbugs-Cc: debbug.1026...@sideload.33mail.com > This is exactly feature that Go upstream provides for a long time. > If you think differently, you should open a "proposal" in Go upstream, > https://github.com/

Bug#1026922: golang-go: The HTTP_PROXY variable is incorrectly implemented to accept SOCKS proxies. HTTP≠SOCKS

2022-12-23 Thread debbug . golang
Package: golang-go Version: 2:1.15~1 Severity: normal X-Debbugs-Cc: debbug.gol...@sideload.33mail.com The go standard libraries apparently include some automatic proxy support for /go/ apps when the HTTPS_PROXY variable is populated. The problem is that SOCKS proxies are accepted. A SOCKS proxy is