Question by Will Boldt · Oct 24, 2018 at 06:39 PM · 398 Views microgateway reverse proxy content-length

Proxy not passing Content-Length to target endpoint

I'm using an Apigee 'Reverse proxy' to call a Third Party API and they say that they are receiving a 'Content-Length' of 0 so they assume the body is empty which is a problem for me. When I call the Third Party API without going through Apigee they are receiving the Content-Length so I know I am sending my request properly.

Is there a reason why Apigee would not be sending the Content-Length to the Third-Party API? NOTE: The content of the request is getting sent, it is just the Content-Length that is the problem.

Add comment Show 1

10 |5000 characters needed characters left characters exceeded

Will Boldt · Nov 02, 2018 at 02:12 PM 0

Link

More Information: Third party let me know that they are receiving the "Transfer-Encoding=chunked" header which is preventing the "Content-Length" header from getting sent. I belive that this is the same problem mentioned in the question "Content-Length gets converted to Transfer-Encoding" which also does not have an answer. Link:

https://community.apigee.com/questions/34164/content-length-gets-converted-to-transfer-encoding.html