Zig Version
0.13.0
Steps to Reproduce and Observed Behavior
I have my local proxy settings:
function proxy_on() {
export http_proxy=http://127.0.0.1:7897
export https_proxy=http://127.0.0.1:7897
export HTTP_PROXY=http://127.0.0.1:7897
export HTTPS_PROXY=http://127.0.0.1:7897
}
function proxy_off() {
unset http_proxy https_proxy HTTP_PROXY HTTPS_PROXY
}
proxy_on
When proxy on:
$ zig fetch https://dist.apache.org/repos/dist/release/opendal/0.50.1/apache-opendal-core-0.50.1-src.tar.gz
error: bad HTTP response code: '400 Bad Request'
$ zig fetch https://codeload.github.com/apache/opendal/zip/refs/tags/v0.50.1
error: invalid HTTP response: EndOfStream
When proxy off:
$ zig fetch https://dist.apache.org/repos/dist/release/opendal/0.50.1/apache-opendal-core-0.50.1-src.tar.gz
1220ca1908d50cedbb20ec2f5aa3da356ec2a28bb7b2aed1d621f3484e382ef27f54
$ zig fetch https://codeload.github.com/apache/opendal/zip/refs/tags/v0.50.1
12201ea7b0bd1b10bcc7f777f0d5bf6c5a5e747ae696cd9c5c122709ad846ef2716f
curl can work on both proxy on and off, so I guess there is some missing proxy handle logic in zig fetch.
Expected Behavior
Since cURL can download artifacts properly, I suppose there are some improvements can be done to let zig fetch succeeds in both scenarios.
Zig Version
0.13.0
Steps to Reproduce and Observed Behavior
I have my local proxy settings:
When proxy on:
When proxy off:
curlcan work on both proxy on and off, so I guess there is some missing proxy handle logic inzig fetch.Expected Behavior
Since cURL can download artifacts properly, I suppose there are some improvements can be done to let
zig fetchsucceeds in both scenarios.