Parse Error: The response headers can't include "Content-Length" with chunked encoding

verosteam · September 9, 2020, 12:23pm

Your question may already have an answer on the community forum. Please search for related topics, and then read through the guidelines before creating a new topic.

Hello everyone,
we are trying to execute a request through a proxy against a web server not managed by us.

Unfortunately, it’s bad designed and currently is not allowing us to execute requests because of some header problems in case of errored requests.

I’ve found an issue on you github support account that has been assigned but not yet replied

github.com/postmanlabs/postman-app-support

Simultaneous headers content-length and transfer-encoding leads to ParseError

opened 03:33PM - 11 Oct 19 UTC

closed 05:46PM - 15 Sep 20 UTC

sbiemont

bug product/runtime

**bug** When both headers `content-length` and `transfer-encoding` are present,… postman raises a `ParseError` and prints the message "Could not get any response". **example** `transfer-encoding: chunked` `content-length: 250` It's not coherent to have these 2 headers in a response (but they can be present). If so, the `content-length` could be used first, without checking the `transfer-encoding`. Or postman could raise a specific error. (?)

There is any way to overcome the following type of error by not touching the proxy in the middle?
Other clients do not have this type of error.

Parse Error: The response headers can’t include “Content-Length” with chunked encoding