On Tue, 15 Feb 2011 10:18:58 +0800, Terry. wrote:
Hello,
A page with its response header as:
(Status-Line) HTTP/1.1 200 OK
Cache-Control no-cache
Connection keep-alive
Content-Type text/html; charset=UTF-8
Date Mon, 14 Feb 2011 11:11:09 GMT
Expires Mon, 14 Feb 2011 11:11:08 GMT
Pragma No-cache
Server nginx/0.8.54
Transfer-Encoding chunked
The page is dynamic, different user should see different content.
But the URL is always the same.
When content varies on user account the content is "private" and should
be marked as such in Cache-Control.
When content is not supposed to be stored by caches it need to be
marked "no-store"
"no-cache" is a slightly fuzzy middle ground which is treated
differently by all browsers and caches. As well as differently when sent
on request and response. It is allowed to be stored and shared around,
but has to be revalidated with the origin before use.
Firefox/IE8/Chrome goes without problem.
But IE7 (and other IE below it I believe) have been caching this
page,
for different people the see the same content.
Once they press "F5" to refresh the page all goes well.
Is this an IE problem? how to prevent the (broken?) IE caching it?
Interesting results. Thank you for mentioning this problem.
Using "private" or "no-store" as appropriate for your content should
fix this problem for all browsers.
Amos
