W3C home > Mailing lists > Public > www-talk@w3.org > May to June 1999

Re: Tracking hits without cache-busting

From: Grahame Grieve <grahame@kestral.com.au>
Date: Tue, 29 Jun 1999 22:07:37 +1000
Message-Id: <>
To: www-talk@w3.org

>>But IE 5 might have a bug regarding this must-revalidate feature: it
>>doesn't redisplay a page when you revisit it from your history with Back
>>and Forward keys until you hit enter in the location field, or something
>>like that.
>That is not a bug in IE5, that is the exact behavior required by the
>standard.  Back is supposed to show the old page you have seen before,
>not fetch a new copy.  See for example section 13.13 of rfc2616.

It's not only IE5 either

but this is obtuse to a user. why should a user perceive 
any difference between a page they got from going back 
and a page they got from going forward? In highly dynamic
web applications this caching of back business is a big problem with 
the http standard

I settle this by trying to prevent the user from 
desiring to use the back button at all. in some ways 
this only makes things worse, of course, but there you go.

my stategies are to provide key links on toolbars and make sure
back links are integrated with the text where the user
would perceive a reason to go back. And I always do a redirect
after a post. has any one got others?

Received on Tuesday, 29 June 1999 08:05:11 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:33:01 UTC