As an important note testing with #3702 the above works as expected. Since the mentioned PR appears to be fixing a different issue I think it's still important to mention here, but please let me know if this should be closed in favor of #3702.
Responses with status codes 1xx, 204 or 304 don't have a response body. For
these, don't parse these headers:
- Content-Encoding
- Content-Length
- Content-Range
- Last-Modified
- Transfer-Encoding
This change ensures that HTTP/2 upgrades work even if a
"Content-Length: 0" or a "Transfer-Encoding: chunked" header is present.
Co-authored-by: Daniel Stenberg
Closes#3702Fixes#3968
I did this
Ran
curl http://localhost:8080 -trace -
against minimal example:I expected the following
Expected curl to terminate, instead hangs permanently or until exited.
Similar issue described in https://serverfault.com/q/870072 from 2017, although doesn't appear to have been reported.
As an important note testing with #3702 the above works as expected. Since the mentioned PR appears to be fixing a different issue I think it's still important to mention here, but please let me know if this should be closed in favor of #3702.
curl/libcurl version
operating system
The text was updated successfully, but these errors were encountered: