When I regenerate the documentation with doxygen (1.8.7) and upload it to the webserver, I always get re-served the same pages as before the upload.
I've tried Ctrl-F5 (FireFox), I've also tried putting the following meta in src/header.html and recompiling doxygen:
<meta http-equiv="pragma" content="no-cache">
<meta http-equiv="cache-control" content="no-cache">
<meta http-equiv="expires" content="-1">
I've also tried using the .htaccess file to control the cache. Unfortunately, I always get served stale html pages.
What am I missing to totally deactivate the cache for doxygen generated html?
Related
I have this Web site: https://fascinatingdreams.com/fd1/index.html. I have set cache behavior to no caching in the meta tags, in the head section of the HTML files of the site, but the site fails to respect those caching directives, and the HTML files load from the cache. Developer tools show that the headers have cache-control: max-age=0.
What I want to achieve is that the HTML pages will not load from the cache.
This is the HTML code that I use to prevent caching of the Web pages:
<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">
Thank you for your answers in advance.
I have the situation where I need to update a static HTML file on a server running WordPress daily. This is referenced by an iframe on a single page.
I would like to prevent the iframe source from being cached, but I can't install a plugin or update WordPress themes.
I had the idea of using a script to set the source to use a query with a random parameter, but I don't believe WordPress allows JavaScript.
I also tried adding the following to the header on the iframe to no avail:
<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" />
Solution was to save the file as a .PHP instead of .HTML
I have an angular2 app where I only want to force reload of the index.html page when the webpage is visited but I don't want to reload all the script files if they have already been downloaded.
Is this possible using a meta tag? e.g.
<meta http-equiv="expires" content="0">
If you use pragma meta, your index.html will not be cached but dependency may be cached anyway :
<meta http-equiv="pragma" content="no-cache">
I generally work with WordPress but just completed a project for a client that was a static HTML page consisting of 8 pages and ~2 images per page. Working with WordPress I would either use w3 total cachce, cloudflare, photon or a solution through wp engine.
I've been doing research and found a few solutions regarding meta tags, and manipulating an .htaccess file. The meta tag route, I read, is not a reasonable solution as it does not validate properly with HTML5. (this was specifically referring to setting up no cache, but same idea)
<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" />
Reference here: Using <meta> tags to turn off caching in all browsers?
I also read a little bit here:
http://www.metatags.info/meta_http_equiv_cache_control
Using something like this:
<meta http-equiv="Cache-control" content="public">
<meta http-equiv="Cache-control" content="private">
<meta http-equiv="Cache-control" content="no-cache">
<meta http-equiv="Cache-control" content="no-store">
But I'm not sure how they actually work and which is the correct one. Can someone point me in the right direction? Thanks!
Step away from the <meta> tags. Default caching headers sent by the web server are, in most cases, already appropriate for a static web site. Unless you have some unusual requirements - which does not appear to be the case here - there should be no need to modify them.
I have a bunch of HTML static files. I realize chrome doesn't really obey the rules in my HTML static file.
<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">
Seems to be bug? http://code.google.com/p/chromium/issues/detail?id=28035
I do not know any workaround. Anyone knows?
Configure your web server to send these as headers for your file (or all *.html files).
Since you didn't specify your web server, can't really give more info.