It is true that an update is only triggered by an "updated" manifest file. But some browsers (FF, chrome) do not check all the files referenced by the manifest file. For example, jpg will not check if the server has a newer one. It appears that the general browser caching policy affects the update process. To force the browser to check all or some of the files in the cache manifest, you must mark these files with "Cache-Control: no-cache" in the HTTP header.
You can control the update operation using cookies. If you have a serveride script that interprets cookie commands, you can make the browser expire the contents of the cache through javascript. For example, if a client executes cache.update () with a set of cache_clear cookies, the server may respond with a response code 404, which causes the browser to expire the contents of the application cache.
iPhAnd
source share