HTML5 - cache manifest working great on Chrome but not on Firefox and Opera
I am developing a web app for offline use, thus I need to use the application cache functionality.
Everything works great on Chrome (15.0.874.106) but is doesn\'t wo
-
You can check the current status of the application cache using
window.applicationCache.status, which returns a numeric value mapped to the following states:0 - uncached,1 - idle,2 - checking,3 - downloading,4 - updateready,5 - obsolete.The application cache API has a few things worth noting:
window.applicationCache.update(): This will trigger the application cache download process, which is nearly the same as reloading the page. It simply checks if the manifest has changed, and if so downloads a fresh version of all the content in the cache (respecting any cache headers). Note that even though a new cache is created with this, the page will continue to use the old cache. To make the page use the new cache you have just downloaded, you must use theswapCache()function.window.applicationCache.swapCache(): This function tells the browser to start using the new cache data if it is available. It is important to note that even if there is a new manifest file, the application will still continue using the old cache (as specified in the old manifest file) untillswapCache()is called. OnceswapCache()is called, then the cache will be used as specified from the new manifest file.from: http://dev.opera.com/articles/view/offline-applications-html5-appcache/
讨论(0) -
As I understand, the Offline Web applications section in the W3C HTML5 draft is non-normative; meaning that is it still not part of the formal HTML5 standard as yet.
Since the feature is still not part of the HTML5 standard, different browsers may have different and varying/non-standard implementations, if at all they choose to implement it. Not all browsers may choose to support it. Do not rely on non-normative features until they are part of the standard.
讨论(0) -
From: http://appcache.offline.technology
In Firefox, any resources served with Cache-control: no-store will not be cached, even if they're explicitly included in the manifest.
My php by default is sending:
Cache-Control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0It is enough to add:
header("Cache-Control: no-cache, must-revalidate");To the php file to get it to start caching it.
(This is similar to Mychal Hackman's answer, but a little more specific).
讨论(0) -
Check your cache in
about:cache. I am betting you will see "data-size 0 bytes" for your PHP file(s).Check your caching headers, I found in Firefox the default was "no-cache" on my php files. I just added:
header("Pragma: public"); header("Cache-Control: public, max-age=6000");to my PHP file and reloaded the offline cache and it is finally working.
HTH
讨论(0) -
To me your cache manifest looks a bit "unusual"... it might help to add a
FALLBACKsection... another point is that the appcache might interfer with the "normal browser cache" i.e. if the cache manifest is changed it needs to make sure that the browser reloads it, ideally this is achieved by changing the name (for example by having version number, timestamp... as part of the name).You can interact in your page with the appcache via JS which could help to pinpoint the problem you see.
For in-depth information including JS code and a thorough walk-through see
- http://www.html5rocks.com/en/tutorials/appcache/beginner/
- http://www.w3.org/TR/html5/offline.html
If need be come back with specific questions.
UPDATE
As per comments provided by OP this shows a nice implementation of the JS API for checking/debugging appcache as described in the links above.
讨论(0) -
For Firefox, try this little trick:
<html manifest="/app/mobile/cache.manifest.php?1">Its the "?1" that finally get Firefox to check for the latest file. That's what did the trick for me anyway. Hope this helps.
讨论(0)
加载中...
- 热议问题