HTTPS_PROXY being ignored

[alextremblay]

Newly installed rbw v 1.10.0 on a host without direct access to the internet

$ rbw --version
rbw 1.10.0

Trying to register rbw against my bitwarden instance accessible only through a web proxy

$ export HTTP_PROXY="http://my_proxy:3128"
$ export HTTPS_PROXY=$HTTP_PROXY
$ export NO_PROXY="localhost"
$ rbw register
# rbw prompts for API key, then times out

In a separate window, i confirm rbw is not contacting my proxy server and is attempting to reach out to my bitwarden instance directly:

$ sudo tcpdump -i ens160 host my_proxy or my_bitwarden
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on ens160, link-type EN10MB (Ethernet), capture size 262144 bytes
12:09:37.636957 IP my_host.53232 > my_bitwarden.https: Flags [S], seq 2642868781, win 64240, options [mss 1460,sackOK,TS val 3337457887 ecr 0,nop,wscale 7], length 0
12:09:38.654697 IP my_host.53232 > my_bitwarden.https: Flags [S], seq 2642868781, win 64240, options [mss 1460,sackOK,TS val 3337458905 ecr 0,nop,wscale 7], length 0
...

I can reach my_bitwarden through my_proxy from my_host with curl, no problem, and when i do, I can see that traffic is flowing through my_proxy:

$ sudo tcpdump -i ens160 host my_proxy or my_bitwarden
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on ens160, link-type EN10MB (Ethernet), capture size 262144 bytes
12:07:34.270797 IP my_host.47024 > my_proxy.3128: Flags [S], seq 3010613948, win 64240, options [mss 1460,sackOK,TS val 1750644005 ecr 0,nop,wscale 7], length 0
12:07:34.271115 IP my_proxy.3128 > my_host.47024: Flags [S.], seq 4269660636, ack 3010613949, win 65160, options [mss 1460,sackOK,TS val 1193057379 ecr 1750644005,nop,wscale 7], length 0
...

All of this seems to point to rbw ignoring HTTP_PROXY and HTTPS_PROXY environment variables.