Issue/bug with wget over https and proxy

Denys Vlasenko vda.linux at googlemail.com
Mon Jan 21 15:46:57 UTC 2019


On Mon, Jan 21, 2019 at 2:53 PM Jakub Ledwoń <ledwojakub at gmail.com> wrote:
> I have env variables set up like this:
> http_proxy=http://proxy_ip:8080
> https_proxy=http://proxy_ip:8080
> ftp_proxy=http://proxy_ip:8080
> When I'm trying to use wget on https link behind this proxy, it fails. On http links it works without issues. I'm using v1.30.0 version of busybox.
>>
>> ./busybox wget https://raw.githubusercontent.com/mirror/busybox/master/INSTALL -O test.txt
>> Connecting to proxy_ip:8080 (proxy_ip:8080)
>> wget: server returned error: HTTP/1.1 502 Bad Gateway
>
> All others standard online console utilities works without issues.
> GNU wget behaves as expected.
>>
>> wget https://raw.githubusercontent.com/mirror/busybox/master/INSTALL -O test.txt
>> --2019-01-21 14:48:42--  https://raw.githubusercontent.com/mirror/busybox/master/INSTALL
>> Connecting to proxy_ip:8080... connected.
>> Proxy request sent, awaiting response... 200 OK
>> Length: 6116 (6.0K) [text/plain]
>> Saving to: ‘test.txt’

We need to compare what is being sent to proxy_ip:8080
bu GNU wget, and by bbox wget. Evidently, there is some difference.

This command should do it:

tcpdump -nl -ieth0 -xX host proxy_ip and port 8080


More information about the busybox mailing list