I have tried all these methods and have seen explorer miss then from time
to time. One problem is that if the page is over 64K the no-cache
directive is ignored. These is a way around this that is guaranteed to
work. Append the current time to the end of the url ts=<currenttime>. This
ts can be ignored by you but it makes the client think that it is
reloading a new page everytime so it will never check the cache.
hope this helps,
Rory
On Thu, 3 Apr 2003, Liam Quinn wrote:
> On 4 Apr 2003, Adrian Caneva wrote:
>
> > Expiration headers seem to be ignored by Internet Explorer behind a Proxy
> > server when using BACK / FORWARD buttons.
> > On Microsoft's Knowledge Base Article 234067 (HOWTO: Prevent Caching in
> > Internet Explorer) I've found that in fact this can happen.
> > And I could verify that, behind a Proxy, IE (6.0, 5.5, 5.0) gets the page
> > from local disk cache although Expire = -1 header should force it ask the
> > web server for an updated version.
>
> FWIW, IE's behaviour seems to be in agreement with the HTTP/1.1
> specification:
>
> By default, an expiration time does not apply to history mechanisms.
> If the entity is still in storage, a history mechanism SHOULD display
> it even if the entity has expired, unless the user has specifically
> configured the agent to refresh expired history documents.
>
> http://www.w3.org/Protocols/rfc2616/rfc2616-sec13.html#sec13.13
>
>
Received on Apr 04 2003
Intro
