|
|
Posted by John Dunlop on 11/17/06 13:39
Mike Scholl:
> I note on some site you get a "this page has expired" message if you try to
> scroll back.
Well, you don't get the message from the server but from your
browser. The reason for it is that some browsers try to re-request
resources accessed through the history list, including POST requests;
and since POST requests are, more often than not, uncacheable, the
browser warns its user about a potentially unsafe interaction.
However, history lists are 'meant to show exactly what the user saw
at the time when the resource was retrieved' (RFC2616 : 13.13); in
other words, going Back is not meant to result in a new request.
http://www.ietf.org/rfc/rfc2616.txt
> How can I do that?
Read up on what cache directives the browser du jour wants.
> Or in some other way prevent outdated data from being displayed.
This is what the history list is _for_. Thankfully, you can't turn
it off.
--
Jock
Navigation:
[Reply to this message]
|