304 not modified response from target causes Apigee to hang

[#1]

When response caching is disabled, a 304 response from the target is received by Apigee and it sits there until there is a timeout at the client instead of forwarding it to the client. Please help...

--SF914487--

[adas]

@Arjav Goswami this should not be the case. Can we get the actual customer bundle that is having this issue. I quickly put together a bundle that has a response cache policy which is disabled and calls a backend that returns a 304 response code and I don't see any issues. I am attaching the bundle so that you can try it out yourself too.

[adas]

@Arjav Goswami Here's the apiproxy bundle you can try out on your org.

[akashtp]

@Arjav Goswami

@arghya das

I have seen a similar issue where a customer was seeing a 502 error when the backend responded with a 304.

Issue was resolved after adding streaming for response as the IIS server in this case was sending empty response and the message processor is waiting to read it.

<Properties> <Property name="success.codes">304</Property> <Property name="response.streaming.enabled">true</Property> </Properties>