Bazel fails to fetch modules when socks5 proxy is used

[oakad]

Description of the bug:

Recent enough Bazel works mostly ok when HTTPS_PROXY env var is set to point to socks5 proxy. However, it breaks on some operations.

Which category does this issue belong to?

Core

What's the simplest, easiest way to reproduce this bug? Please provide a minimal example if possible.

There's an ssh socks session listening on port 5000, confirmed working

export HTTPS_PROXY=socks5://localhost:5000

Attempting to build a random project

bazel build ....

Starting local Bazel server and connecting to it...
ERROR: Error computing the main repository mapping: Error accessing registry https://bcr.bazel.build/: Failed to fetch registry file https://bcr.bazel.build/modules/rules_java/7.6.1/MODULE.bazel: Proxy address socks5://localhost:5000 is not a valid URL
Computing main repo mapping:

Which operating system are you running Bazel on?

Linux

What is the output of bazel info release?

release 7.2.1

If bazel info release returns development version or (@non-git), tell us how you built Bazel.

No response

What's the output of git remote get-url origin; git rev-parse HEAD ?

No response

If this is a regression, please try to identify the Bazel commit where the bug was introduced with bazelisk --bisect.

No response

Have you found anything relevant by searching the web?

No response

Any other information, logs, or outputs that you want to share?

No response