W3C home > Mailing lists > Public > www-talk@w3.org > March to April 2000

Re: Enforce reloading of page when using the back-button

From: Grahame Grieve <grahame@kestral.com.au>
Date: Wed, 08 Mar 2000 09:43:02 +1100
Message-Id: <4.1.20000308094254.0394d100@10.252.1.60>
To: www-talk@w3.org
Hi Dan

>Umm... I suppose there are relevant hacks; maybe even standard
>techniques. But would you please assure us that you understand
>how inconvenient this is for users, and that you have a darned
>good reason for doing this, before we discuss the technical
>details?

This was discussed before on this list. I write (or at least I 
try) full blown applications using http/html.  The fact that I 
can't tell the browser not to cache the back button is a right 
pain and it would be perfectly appropriate for me to prevent 
this for my application.

However the standard does not specify any way for me to prevent 
this caching, nor I have I found any work-arounds. The browsers 
cache so aggresively... and the standard says they should in this 
case. Which I understand as being appropriate for the vast 
majority of cases. 

Last time this was discussed someone on the http working group(?) 
contributed and said that there had been some discussion about a 
header that could prevent caching on the history trail, but it 
had not met with sufficient acceptance in the group to become 
included in the standard. sigh.

However this...
>	1. Breaking or Slowing Down the Back Button
>	[...] "

suggests that it's possible. Does anyone know how?

Grahame
Received on Tuesday, 7 March 2000 17:52:15 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 27 October 2010 18:14:24 GMT