Ensuring 'freshness' of dynamic pages (slightly offtopic)
Hi guys, I've been trying to ensure that documents from a certain website are always fresh, that is, every request for a new page must be validated before the client sees it. I've tried using these HTTP Cache-control directives: no-cache no-store max-age (1) must-revalidate but no such luck. If I for example specify 'Check against server: Never' in IE, the pages are cached, no matter what. Is it possible to ensure that pages are always fresh, even if it is specified on the client side that the client should never try to retrieve a 'fresher' page? I've been contemplating a new solution, which is to append a string like ?ensure_freshness=02349025180.12 (some random, unique id) on each link, but that's not a thing which I wish to do now, at such a late stage in the project. Also, it strikes me that it isn't possible to specify multiple cache-control directives with the current HTTPRequest implementation, am I missing something here, or is this a bug / missing feature? Any ideas? Thanks, Morten
On Sun, 11 Mar 2001, Morten W. Petersen wrote:
but no such luck. If I for example specify 'Check against server: Never' in IE, the pages are cached, no matter what.
Is it possible to ensure that pages are always fresh, even if it is specified on the client side that the client should never try to retrieve a 'fresher' page?
In my experience, IE cache control is badly broken. Using the random id in the URL is, as far as I've been able to figure out, the only way to *guarantee* a fresh grab. There have been several discussions of this problem on the mailing list in the past, and you can certainly experiment with all of the suggestions that have been floated...but I don't know of a definitive solution other than the random id. --RDM
"Morten W. Petersen" wrote:
Is it possible to ensure that pages are always fresh, even if it is specified on the client side that the client should never try to retrieve a 'fresher' page?
Send an "expiration" header with a valid date that has already passed. This has always worked for me, even in old browsers. Please tell me this still works. :-) Shane
"Morten W. Petersen" wrote:
Is it possible to ensure that pages are always fresh, even if it is specified on the client side that the client should never try to retrieve a 'fresher' page?
Send an "expiration" header with a valid date that has already passed. This has always worked for me, even in old browsers. Please tell me this still works. :-) Shane
participants (3)
-
Morten W. Petersen -
R. David Murray -
Shane Hathaway