Hi,
There are some cache-control HTTP headers that may do the trick.
I think they are mainly designed for use by intermediate proxy-servers
which do cacheing, but the browsers may use them as well.
Pragma: no-cache (HTTP 1.0)
Cache-control: no-cache (HTTP 1.1)
Expires: Fri, 14 Jul 2000 09:48:54 GMT (HTTP 1.0)
You should experiment to see how they work.
Of course, this solution would cause the browser to never cache the
page. The "Back" button would always cause a request to the server.
Some JavaScript trick may be employed if an action on a screen
conditionally invalidates one of the history entries, forcing a
new request when you browse "Back" to it.
Stephen
At 09:19 AM 7/14/00 +0000, you wrote:
>I am looking for a way to invalidate pages after the information that
>has generated them changed. For example: a user does query which
>returns a list of contacts. The user then clicks on the contact and
>modifies the contact name. Then, they click on the back button and see
>the name spelled the old way in the search results. How I do I make it
>so the page comes up and says that it has expired. Or better yet, have
>it automatically refresh.
>
>Thanks,
>
>Dan Diephouse
>
>
>
>------------------------------------------------------------
>To subscribe: [EMAIL PROTECTED]
>To unsubscribe: [EMAIL PROTECTED]
>Search: <http://www.mail-archive.com/turbine%40list.working-dogs.com/>
>Problems?: [EMAIL PROTECTED]
>
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Search: <http://www.mail-archive.com/turbine%40list.working-dogs.com/>
Problems?: [EMAIL PROTECTED]
