yep! both of these work pretty well! and will work for ANY browser!
Miikka Leskinen wrote:
On Thu, 28 Apr 2005 16:28:59 +0300, "Miikka Leskinen" <[EMAIL PROTECTED]> said:
On Thu, 28 Apr 2005 16:46:00 +0400, "Louis Suarez-Potts" <[EMAIL PROTECTED]> said:
http://www.justis.com/support/faq-cache.html#firefox
thanks. But I meant is there something we could write into our pages that forces a user's firefox to refresh its cache?
<meta http-equiv="Pragma" content="No-Cache" />
This could do it. It tells the browsers that cache shouldn't be used, but the request should be made directly to the server.
It's HTTP-EQUIV which means that it's meant for the server. In other words: server configuration that the server catches from the XHTML code (like Content-Type and all that). So check that the server is really reading these META tags.
Don't know how this works in practice though. :) I think the cache-or-no-cache choice should be made by the user agent, not the server (??).
Oh, forgot to mention...
You can also try <meta http-equiv="Expires" content="0" />.
It means the page immediately expires in the cache. This way, the browser should always consider using the cache as a bad choice and always fetch the page from the server instead.
But that's more like a hack, and not a "real" solution (abuse of "Expires" meta tag).
best Louis
Miikka Leskinen miles_fin
Regards, Miikka Leskinen
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
-- =========================================================== Kay Schenk
"Here's all you have to know about men and women:
women are crazy, men are stupid.
And the main reason women are crazy is that men are stupid."
-- George Carlin--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
