HTTP/1.1 Transfer-Encoding uses wrong Content-Length handling #7643
As laid out in RFC 7230 section 3.3.3
As the spec (clarified like this long after curl's initial implementation) says
Transfer-Encoding for anything else but chunked is rarely used, which is probably why this hasn't been reported earlier.
Right now, curl acknowledges and uses the content-length as the size of the compressed presentation in the body.
The text was updated successfully, but these errors were encountered: