Hi,
I am in the process of putting one of our existing API's behind the EMGW. For the most part it works out of the box but I am encountering issues when proxying POST requests on to an OpenRasta based backend.
Some digging revealed that OpenRasta does not handle Transfer-Encoding well, while the EMGW seems to convert all POST requests to Transfer-Encoding, even if the original request specified Content-Length
To migrate the OpenRasta based service to one of the other frameworks we currently use will take some time so I am wondering if it is possible for me to instruct EMGW to retain the Content-Length header once it has been specified on the original request.
Should the EMGW behaviour be as mentioned here: https://apigee.cloud.answerhub.com/questions/5831/how-does-api-proxy-decide-whether-to-use-transfer.... ?
David
LinkedIn
Twitter
