[Seaside] Re: Re: How to mark not-cacheable?
Randal L. Schwartz
merlyn at stonehenge.com
Thu Jan 17 05:59:04 UTC 2008
>>>>> "itsme213" == itsme213 <itsme213 at hotmail.com> writes:
itsme213> In fact, is there any way to do this re-generation right when the
itsme213> back button is pressed, as opposed to after the user clicks on the
itsme213> backed-up page? (I am under the impression that "Back" requires a
itsme213> server request if the earlier header said do-not-cache, so perhaps
itsme213> this is possible).
I think you were told earlier that "do not cache" has NOTHING to do with
compliant browsers. It's strictly for caching web proxies. Do not confuse
IE's misinterpretation of the header with what it was intended for.
NOTHING stops a web browser from caching a web page and presenting it to the
user a second time once the "back" button is pressed, without *any* net
traffic. This is as it should be. It's your job (as was already pointed out)
to ignore any callbacks that no longer make sense, either because of the
current conversation *or* some other conversation elsewhere that invalidates
the callback as well.
Randal L. Schwartz - Stonehenge Consulting Services, Inc. - +1 503 777 0095
<merlyn at stonehenge.com> <URL:http://www.stonehenge.com/merlyn/>
Perl/Unix/security consulting, Technical writing, Comedy, etc. etc.
See PerlTraining.Stonehenge.com for onsite and open-enrollment Perl training!
More information about the seaside