[Javascript] Client Side anti-cache [was 1 MORE Question...]

[javascript@xxxxxxxxxx (Rees, Mark (TWIi London))]

Hello

One other thing you might try is to append a unique querystring to each
page. If you are using sessions in your shop for example and there's no
security risk then you could drop that on the end of the querystring, the
result being that the browser will (as far as I know) think it's a different
page and download it again, so
page.asp?x=0
is not the same as
page.asp?x=1

Cheers

Mark

-----Original Message-----
From: Ben Curtis [mailto:Quixote@xxxxxxxxxxxx]
Sent: 26 June 2001 18:50
To: javascript@xxxxxxxxxx
Subject: Re: [Javascript] Client Side anti-cache [was 1 MORE
Question...]




> I wonder what the difference is between "Automatically"
> and "Every visit to the page". For example would
> "Automatically" just check on Tuesdays, unless the moon
> was full?

"Automatically" compares the date last modified of the file on the server to
the date last modified of the file in cache, and takes the more recent of
the two. This is made complex by intervening proxy caches which store
incorrect dates or make a bad guess as to when it should refresh the data,
as well as by simple human-error problems like servers with the date
incorrectly set, and so forth.

Also, client-side caching is not the only caching problem. I have had
extensive problems with educational institutions and large businesses
caching pages so that one person sees another's pages. The solution to this
is to put forth some cache-control headers server side and hope for the
best.

+Ben Curtis

"One of the symptoms of an approaching nervous breakdown
is the belief that one's work is terribly important."
- Bertrand Russell (1872-1970)







_______________________________________________
Javascript mailing list
Javascript@xxxxxxxxxx
http://www.LaTech.edu/mailman/listinfo/javascript