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. 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.



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/golang/proposal#the-proposal-process

“Feature” is the wrong word here. Use of incorrect terminology &
misstating a usage is a plainly obvious defect. The incorrectness of
(e.g.) calling a “potato” a “tomato” leaves no room for
subjectivity. It’s a bug. Consequently, a bug report was filed (not a
feature proposal).

To say it’s been that way “a long time” is known as a /Conventional
Wisdom/ fallacy. The bug does not become less of a bug over time. The
only effect that time has in this case is to do more damage, as more
and more code creates dependencies on the defect. Go lang itself is
also a quite young language, coming into existence in 2009. So nothing
about the language has existed for “a long time”.

Directing users to report bugs upstream goes against Debian
conventions. It’s the duty of the maintainer to mirror bugs upstream:

  https://www.debian.org/Bugs/Reporting

Not everyone has MS Github. Not everyone is willing to have
transactions with Microsoft. I cannot login to Github because the 2fa
process forces me to check an account that blocks access to the
verification code with a broken CAPTCHA.

Please follow the Debian procedure and mirror this bug report
upstream; not as a proposed new feature but as a bug report.

Thank you.