Browser is displaying no-cache version of page after receiving HTTP 304

Asked Dec 29 '11 at 10:48

Active Dec 30 '11 at 09:29

Viewed 218 times

It happens in my Wordpress and nginx configuration but IMO it's browser/HTTP related problem.

Everything is about one page, that appears in two versions, for logged in user and anonymous user. Scenario:

Wordpress is serving user page that should be cached (HTTP 200)
Wordpress is serving, for logged in user, a page that should NOT be cached (HTTP 200 with no cache header).
After logging out, I want user to receive page no 1, but he is getting page no 2 from browser cache. Nginx is sending HTTP 304, so the browser should take last cached page from browser memory or from the server. But it's not happening.

These are HTTP headers for above cases: http://pastebin.com/nJAxLQSq

edited Dec 30 '11 at 09:29

asked Dec 29 '11 at 10:48

Tuner

Please provide traces of the headers sent for (1) and (2). – Julian Reschke Dec 29 '11 at 13:22
These are the HTTP headers for all of 3 cases: http://pastebin.com/nJAxLQSq – Tuner Dec 30 '11 at 09:29
Interesting. One odd thing I noticed is that response 2. doesn't have "Vary: Cookie". Do all browsers show the same behavior? – Julian Reschke Dec 30 '11 at 16:07

0 Answers0