This website uses Cookies. Click Accept to agree to our website's cookie use as described in our Privacy Policy. Click Preferences to customize your cookie settings.
Accept
Reject
Preferences
Log in to ask a question
Log in to ask a question

For 304 status code from services the gateway takes a long time to return response

Posted on 07-11-2019 12:56 PM
revmuthu
New Member
Reply posted on --/--/---- --:-- AM

I've implemented supporting If-Modified-Since header for my APIs (https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/If-Modified-Since) within my web service and do notice that for the cases where the response had empty body esp., with status code 304 the gateway was responding after 6000ms 😞 Not sure what can be done at the gateway policy to circumvent this

0 2 806
Topic Labels
0 Likes
2 REPLIES 2

Posted on --/--/---- --:-- AM
cjking
Staff
Reply posted on --/--/---- --:-- AM

If you can reproduce this, you should take a trace to see what exactly is causing the latency. The trace will tell you which policy (or policies) are causing the delay and you can troubleshoot from there.

Posted on --/--/---- --:-- AM
ahorner
New Member
Reply posted on --/--/---- --:-- AM

We were running into this same issue with HTTP 204 and 304 responses from origin. The fix is to remove the Content-Encoding response header at origin when these status codes are sent. I'm assuming that Apigee opens a gzip reader when Content-Encoding is set but there are no response bytes in the body so the gzip reader times out after 30 seconds (in our case). Good luck!

0 Likes