Nginx Error 500 page no-cache

Question

This doesn't make much sense, but it seems like when nginx serves up an error 500, it sends along a header that the client shouldn't check for new content the next time it connects.

I can get around it by refreshing, but some of my users have to fully clear their cache after they've hit it.

Is this the default functionality? And if so is there a way to prevent nginx from doing this?

If it makes a difference, it seems to happen when I'm restarting the Gunicorn process that nginx connects to to get the content.

`it sends along a header that the client shouldn't check for new content the next time it connects.` please put some evidence/indication of what you mean there - like the output of `curl -i http://example.com/should-be-a-500` — AD7six, Jun 25 '15 at 13:32

score 2 · Accepted Answer · edited Apr 13 '17 at 12:14

2

I found this answer from a different question and it solved my problem. It's worth noting though, it required updating to the latest version of nginx. It is mentioned in the comments but it is not immediately obvious.

edited Apr 13 '17 at 12:14

Community

1

answered Jun 25 '15 at 13:23

Luke Sapan

189
1
2
15

Nginx Error 500 page no-cache

1 Answers1