Open Vernoxvernax opened 6 months ago
One clear difference is it seems like different versions of libcurl is being used under the hood on the different machines. Would it be possible to capture the output of isahc::version()
on each machine separately for comparison?
One clear difference is it seems like different versions of libcurl is being used under the hood on the different machines. Would it be possible to capture the output of
isahc::version()
on each machine separately for comparison?
Working with:
isahc/1.7.2 (features:default,encoding-rs,http2,json,mime,serde,serde-json,static-curl,text-decoding) libcurl/8.0.1-DEV OpenSSL/3.3.0 zlib/1.3.1 nghttp2/1.45.0
Not working with:
isahc/1.7.2 (features:default,encoding-rs,http2,json,mime,serde,serde-json,static-curl,text-decoding) libcurl/8.6.0-DEV OpenSSL/3.3.0 zlib/1.3.1 nghttp2/1.61.0
Then, I ran cargo update
on both machines, now the system that was working before, does not work anymore and also shows:
isahc/1.7.2 (features:default,encoding-rs,http2,json,mime,serde,serde-json,static-curl,text-decoding) libcurl/8.6.0-DEV OpenSSL/3.3.0 zlib/1.3.1 nghttp2/1.61.0
@sagebind
I was able to observe the same issue in the latest debian bookwork-slim docker image link.
Additionally I ran apt install libssl-dev curl
.
Hope this helps.
Sorry, if im mistaken, but it seems that something somewhere changed, so that it's no longer possible to send POST requests with an empty body. They will just time out. I went through the last few commits, but they don't seem to change the versions of the dependencies. Yeah, I know that was all really vague, but here is the kicker: The problem occurs only on some of my pcs. Even though the curl/rust-toolchain versions match. My guess is, that it's a link to some c library or something. As you can tell my knowledge already ended when I clicked
New issue
, so I'll just leave you these two logs:Working here:
Not working here:
The Code (simplified):
The Fix: