How do I force Google Chrome to ignore data stored in its cache?
I have tried the following to no avail:
<meta http-equiv="cache-control" content="no-store, no-cache, must-revalidate" />
<meta http-equiv="pragma" content="no-store, no-cache" />
<meta http-equiv="expires" content="0" />
Related
Trying to avoid my main page using cache generated by /sub.
Main page is in html, getting code from flask. and i have removed some "levers" to hide information for non members. /sub with member content is in .asp.
Doing a fresh load without cache stored: the web page hides the lever, but when i enter /sub toggle the "lever" and logout (redirected to main). the "lever" is not there but it is toggled on there too.
tried this in html: (the bottom 2 were already included in sentrylogin`s login form but did not effect the "lever")
<meta http-equiv="Cache-Control" content="no-cache, no-store, must-revalidate" />
<meta http-equiv="Pragma" content="no-cache" />
<meta http-equiv="Expires" content="0" />
and :
<meta http-equiv="CACHE-CONTROL" content="NO-CACHE">
<meta http-equiv="PRAGMA" content="NO-CACHE">
in .asp this is already implemented :
<META HTTP-EQUIV="CACHE-CONTROL" CONTENT="NO-CACHE">
<meta http-equiv="CACHE-CONTROL" content="NO-CACHE">
<meta http-equiv="PRAGMA" content="NO-CACHE">
basicly i want the .html file to ignore all cache, dont make any, dont get any. if that works. are there some better commands?
When my server renders index.html, it injects some cache busting witchcraft there so that scripts are forced to reload if the version changes. If I do nothing, mobile Chrome wont even bother to ask if there is a new version of index.html.
If I add the following to the rendered index.html
<!-- never cache this locally -->
<meta http-equiv="cache-control" content="max-age=0" />
<meta http-equiv="cache-control" content="no-cache" />
<meta http-equiv="expires" content="0" />
<meta http-equiv="expires" content="Tue, 01 Jan 1980 1:00:00 GMT" />
<meta http-equiv="pragma" content="no-cache" />
It does fetch / again but as an unwanted side effect it also caches none of the scripts even though the version number stays the same.
This did the trick.
<meta http-equiv="expires" content="0" />
As did the previous answer that was deleted, I just had disable cache on in the devtools.
I have been done a quite lot of research on the internet discovering the influence and support of different caching metatags.
The following metatags cover all the browser support for not caching as been answered here:
<meta http-equiv="cache-control" content="max-age=0" />
<meta http-equiv="cache-control" content="no-cache" />
<meta http-equiv="expires" content="0" />
<meta http-equiv="expires" content="Tue, 01 Jan 1980 1:00:00 GMT" />
<meta http-equiv="pragma" content="no-cache" />
After doing a lot of research I found that there are lot of contradictions in what people say. Some say the <meta http-equiv="pragma" content="no-cache" /> is not supported anymore after IE 6 and Firefox and Chrome does not ever support this.
Could anyone tell me or give me a clear explanation, perhaps with references (http vs https), which metatags are (not) supported in which browser? That would help me and I think other people as well! Thank you
For security reasons, we don't want someone's submitted info to be stored. For instance, after coming to a page via a form submit, when I refresh, it asks if I want to send that same data again (at least in Chrome).
We're attempting to create a session-ish behavior. We're not maintaining a server session - after log in, the user gets a single page returned. Since there are no other pages for the user to navigate to once logged in (no server calls at all) it seemed simpler to handle it this way. However, refreshing the page allows the data to be resubmitted, we don't want that. You can also click the back button, then the forward button, and the page is still there, or go on to other sites, and back-button back to the page.
I found <meta http-equiv="CACHE-CONTROL" content="NO-CACHE"> but it doesn't seem to be having any effect.
Javascript solutions are acceptable, as javascript is required (not by me, don't shoot the messenger) for access.
Thanks!
In order to insure that the page wont cache you need to place another set of 'HEAD' tags at the bottom of the document aswell.
For example:
<HTML>
<HEAD>
<TITLE>No Cache</TITLE>
<META HTTP-EQUIV="Pragma" CONTENT="no-cache">
<META HTTP-EQUIV="Expires" CONTENT="-1">
</HEAD>
<BODY>
...
</BODY>
<HEAD>
<META HTTP-EQUIV="Pragma" CONTENT="no-cache">
<META HTTP-EQUIV="Expires" CONTENT="-1">
</HEAD>
</HTML>
source
-- or --
<meta http-equiv="cache-control" content="max-age=0" />
<meta http-equiv="cache-control" content="no-cache" />
<meta http-equiv="expires" content="0" />
<meta http-equiv="expires" content="Tue, 01 Jan 1980 1:00:00 GMT" />
<meta http-equiv="pragma" content="no-cache" />
The specified date should be a date in the past so that the browser will immediately discard the cached copy or not cache it at all.
I have a page with another html page in iframe. In this iframe, i put this header tag
<META http-equiv="Pragma" content="no-cache">
<META HTTP-EQUIV="Expires" CONTENT="-1">
<meta http-equiv="cache-control" content="no-cache" />
But chrome still cache it, when iframe content changed, hit f5 button but chrome still load cached version, not new version.
Please tell me how to pevent google chrome cache this iframe.
Set the correct expiry headers in the HTTP response from your server. They override anything you've put in meta tags.
This works in Chrome:
<meta http-equiv="cache-control" content="max-age=0" />
<meta http-equiv="cache-control" content="no-store" />
<meta http-equiv="expires" content="-1" />
<meta http-equiv="expires" content="Tue, 01 Jan 1980 1:00:00 GMT" />
<meta http-equiv="pragma" content="no-cache" />
I found this in a Chromium bug.
https://bugs.chromium.org/p/chromium/issues/detail?id=28035
Meta tags can be ignored. Instead of them your server should set appropriate HTTP headers for cache control. You should also set the Expired header.
https://en.wikipedia.org/wiki/List_of_HTTP_header_fields#Avoiding_caching
I found that Chrome may ignore those meta settings in the file in favor of the cache settings in http response header. I was able to fix this issue in IIS by adding this in my web.config
<system.webServer>
<staticContent>
<clientCache cacheControlMode="NoControl" />
Files still get cached but now I can explicitly exclude a file if I need to.