Re: Problem forcing pages not to cache.

Scripsit damiensawyer@xxxxxxxxxxxx:

I have a requirement to ensure that pages do not store anywhere in the
browser cache.

It cannot be guaranteed. However, the tags you have used are a reasonable attempt. Any browser that refuses to honor any of them won't listen to you anyway as regards to caching. It wouldn't hurt, however, to try to do cache control at the level where it logically belongs, namely HTTP level, in HTTP headers. In particular, this could be effective against some proxy caches (which won't even look at any <meta> tags). Check the classic reference, "Caching Tutorial for Web Authors and Webmasters", http://www.mnot.net/cache_docs/

Essentialy, when the user hits logout, the information
they've been reading needs to be completely innaccesable.

This cannot be guaranteed, of course. In particular, you cannot erase it from the user's mind, or print copies, or locally saved copies.

I have done a bit of Googling and found articles suggesting the
following HTTP-EQUIV meta tags.

There are some mistakes and questionable features in them. For example, Cache-Control header uses, by the protocol, commas and not semicolons as separators.

The page loads and validates via WC3,
however fails to secure the content.

Validation is just formal and says nothing about the correctness of the contents in the <meta> tag attributes.

I'm testing in Firefox 2 by opening the below file from a local disk.

I would not expect a browser cache local files anyway, by default. What would be the point?

I then leave the page, set the browser to 'work offline' and open the
file from 'history'. The page appears in full. I have also tested the
file served via http from a web browser to the same result.

So what? The history is a collection of URLs, and when you open something via the history, the browser accesses the resource by its normal rules. This includes reading it from disk if it is local, as well as requesting it via HTTP when its logic so requires (that is, the page is not in the cache or the caching information tells that the cached copy is to be treated as expired).

--
Jukka K. Korpela ("Yucca")
http://www.cs.tut.fi/~jkorpela/

.

Relevant Pages

  • Re: Serious cache problem - Page_Load get never get called !!!
    ... > cache the page. ... That's correct -- the HTTP spec distinguishes between caches and histories. ... > meta tag may help catch more browsers than just the response header ... you name any modern browser for which a META tag works, ...
    (microsoft.public.dotnet.framework.aspnet)
  • Re: Squid Overkill? (Speed Up Web Surfing)
    ... Each user's browser already maintains a cache of web ... Squid cache. ... The first local user to access a web site on a distant web server will ...
    (comp.unix.bsd.freebsd.misc)
  • RE: Disable cache in mobile Web Page
    ... page in the cache, but the problem is how if there are so many different ... > mobile internet tool kit and ASP.net. ... > I have tried every code or script,but it didn't work.I think the answer is related with machine configjust like Simon Calver said. ... More specifically do you know the browser and version on ...
    (microsoft.public.dotnet.framework.aspnet.mobile)
  • RE: Avoid Cache in Mobile Web Page
    ... page in the cache, but the problem is how if there are so many different ... > mobile internet tool kit and ASP.net. ... > I have tried every code or script,but it didn't work.I think the answer is related with machine configjust like Simon Calver said. ... More specifically do you know the browser and version on ...
    (microsoft.public.dotnet.framework.aspnet.mobile)
  • Re: Some cache ideas
    ... using the cache block LRU information means indexing ... I am not certain how the POWER6 predictor ... Yes, indexed by register number. ... other sets' tags must be checked. ...
    (comp.arch)