views:

2496

answers:

4

I'm currently using a Cache Manifest (as described here). This effectively makes the necessary resources to run the application available when the user is offline.

Unfortunately, it works a little too well.

After the cache manifest is loaded, Firefox 3.5+ caches all of the resources explicitly referenced in the cache manifest. However, if a file on the server is updated and the user tries force-refreshing the page while online (including the cache-manifest itself), Firefox will absolutely refuse to fetch anything. The application remains completely frozen at the last point it was cached. Questions:

  1. I want Firefox to effectively only rely on the cached resources when the network connection fails. I've tried using the FALLBACK block, but to no avail. Is this even possible?
  2. If #1 is not possible, is it possible for the user to force-refresh a page and bypass this cache (ctrl-F5 doesn't do it and neither does clearing the browser's cache, shockingly) short of clearing their private data? Alternatively, does the cache-manifest mechanism support expiry headers and is its behavior with respect to this documented anywhere?
+7  A: 
Justin Searls
+1  A: 

Disclaimer: my experience with manifests and cache is all Safari and FF may handle some things differently.

  1. You are quite right. If there are any files listed on the manifest that can't be found, no caching will occur.

  2. Even if you are online, the browser will check only the manifest file. While waiting for the manifest file, it will continue to load the site from the cache - that way it doesn't delay rendering - but it means that you don't see any changes on the first load.

  3. The next time the site is loaded, if the manifest changed on the previous load, the new files will be loaded.

IT IS ALWAYS NECESSARY TO RELOAD TWICE to see any changes. In fact, I have sometimes had to reload 3 times to see the update. No idea why.

When debugging, I generate my manifest file on the fly with php, so there is no chance of a typo in a filename. I also generate the version number randomly each time to force an update but still have an offline webapp for testing.

Once complete, the php file can just echo the saved manifest data with a constant version number and the cache will always be used.

Just some things I have learned while playing with manifest and cache recently. It works great, but can be confusing.

There is no expiry. To uncache, you have to change the manifest file to have nothing in it and do a reload. On Safari, clearing the user cache does clear out all cached files.

GeoNomad
Mirrors my experience in FireFox almost exactly, except for the fact that clearing the user cache in Safari apparently clears the HTML cache. Thanks for your input.
Justin Searls
I've had a very similar experience with over-caching and it refusing to clear the cache. Quite a few times in Safari (on both the desktop and mobile devices) I have had to either open a new tab in the browser (on the desktop) or reboot the device (on the iPad) to force a reload when it's gotten "stuck" for some unfathomable reason. I find trapping all update events quite useful for identifying this (e.g. when it starts to check for an update but never fires an "update complete", "progress" or "error" event I know right away it's a problem with the client, not the app).
Iain Collins
Oh, and interesting thing in Firefox (possibly other browsers) - changing a commented out line in the manifest (an approach Apple's developer documentation recommends) DOESN'T cause it to trigger an cache update. You *must* to add or remove a line with an active instruction (e.g. actually add or remove an entry for a file from the cache manifest) before it will recognise the manifest has updated.
Iain Collins
A: 

Hmm, I just called update() on the cache, after making an edit change to the manifest file, and received the full sequence of check/downloading/ready, did one reload, and a text change I had made in one of my js files, that shows up in the initial page of my app, promptly appeared.

Seems I only need one reload.

BobFromBris
A: 

I made an Firefox add-on which invalidates the Cache Manifest and clears HTML5 Local Storage.

http://sites.google.com/site/keigoattic/home/webrelated#TOC-Firefox-HTML5-Offline-Cache-and-Loc

You can also invalidate the cache manifest by typing the code below in the Error Console:

// invalidates the cache manifest
var mani = "http://.../mysite.manifest"; // manifest URL
Components.classes["@mozilla.org/network/application-cache-service;1"].getService(Components.interfaces.nsIApplicationCacheService).getActiveCache(mani).discard();

Or, by typing the code below in the address bar will manually enforece the cache to be updated:

javascript:applicationCache.update()
keigoi
Thank you! your plug in is a little difficult to install, but it works wonderfully!
Abel Tamayo