I have a web site where I added a CACHE MANIFEST file. This was to ensure that full-screen web apps in iOS wouldn't fetch things from cache. (Otherwise, they seem to refresh HTML properly, but not linked JavaScript or CSS.) In my application, off-line access is totally useless, so I created the manifest to not cache anything. Here's what it looks like:
CACHE MANIFEST
# Version 1.0
NETWORK:
*
This fixed my issues in iOS, but it seems to mess up Chrome (40.0.2214.115 m). Chrome insists on always fetching my base html file from cache even with the development tools open and "Disable cache" checked. If I can simply remove/rename the cache manifest file and refresh, that fixes the problem. In addition, my base HTML file has these headers:
<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"/>
Is there something I am missing here? Seems odd that Chrome would do more caching when I have a manifest file present that says to do no caching.
This behavior has been fixed in Chrome 41.0.2272.76 m. It no longer fetches files from cache for my site with the manifest file.