Get hands-on experience with 20+ free Google Cloud products and $300 in free credit for new customers.

Why I got "errorcode":"protocol.http.ResponseWithBody" if the response has no body?

Hi,

I have the following problem. I have a FuseESB as target endpoint of one of my proxy. When I make a call to the Fuse webservice directly everything works fine and the response is:

HTTP/1.1 204 No Content Date: Wed, 19 Oct 2016 08:01:04 GMT Server: Jetty(8.1.17.v20150415) Transfer-Encoding: chunked Content-Length: 0 Keep-Alive: timeout=2, max=256 Connection: Keep-Alive Content-Type: text/plain; charset=UTF-8

When I call the webservice through the apigee proxy, it blocks that answer and respond back:

HTTP/1.1 502 Bad Gateway Content-Type: application/json Date: Wed, 19 Oct 2016 08:02:02 GMT Server: Apigee Router Content-Length: 123 Connection: keep-alive {"fault":{"faultstring":"Received 204 Response with message body","detail":{"errorcode":"protocol.http.ResponseWithBody"}}}

It seems that the proxy see a body in the response, but there is no body actually. Anyone can help to solve?

0 4 773
4 REPLIES 4