Daniel Stenberg 于2020年6月16日周二 上午5:44写道：
>
> On Sun, 14 Jun 2020, Hongyi Zhao via curl-users wrote:
>
> > On Ubuntu 20.04
>
> I presume that's curl 7.68.0 ?
>
> > $ curl -L -x socks5h://127.0.0.1:10119
> > http://speedtest-ny.turnkeyinternet.net/1000mb.bin >/dev/null
> > % Total% Received % Xf
Daniel Stenberg 于2020年6月16日周二 上午5:44写道：
>
> On Sun, 14 Jun 2020, Hongyi Zhao via curl-users wrote:
>
> > On Ubuntu 20.04
>
> I presume that's curl 7.68.0 ?
$ curl --version
curl 7.68.0 (x86_64-pc-linux-gnu) libcurl/7.68.0 OpenSSL/1.1.1f
zlib/1.2.11 brotli/1.0.7 libidn2/2.2.0 libpsl/0.21.0 (+libid
On Mon, 15 Jun 2020, WGH via curl-library wrote:
When debugging some issue regarding possibly broken gzipped HTTP response in
Go[1], I noticed that curl has no problems decompressing it, and returns
successful exit code.
...
Does anyone has a clue what's going on? Does curl erroneously not r
On Sun, 14 Jun 2020, Dorit Mari via curl-library wrote:
I use libcurl version 7.65.3. The OS is Linux. I always use CURLOPT_RESOLVE
...
libcurl compiled without this flag (45% vs. 12%).
Wow, that's seem super strange. How on earth can the resolving code - that you
don't even use - affect
On Sun, 14 Jun 2020, Hongyi Zhao via curl-users wrote:
On Ubuntu 20.04
I presume that's curl 7.68.0 ?
$ curl -L -x socks5h://127.0.0.1:10119
http://speedtest-ny.turnkeyinternet.net/1000mb.bin >/dev/null
% Total% Received % Xferd Average Speed TimeTime Time Current
HMAC Authorization Headers, like Amazon's AWS v2, encode the 'Date:' header
in the calculation allowing requests to have a TTL.
Currently we are generating the 'Authorization:' header before submitting
the easy handle to our multi handle. While this has been working for us,
we've had several event
Hello!
When debugging some issue regarding possibly broken gzipped HTTP response in
Go[1], I noticed that curl has no problems decompressing it, and returns
successful exit code.
$ curl -s https://regexr.com/ --compressed >/dev/null; echo $?
0
However, the compressed data appears to be b
