781685 - AppCache updates must trigger a manifest update

Status: RESOLVED WONTFIX

(Core Graveyard :: DOM: Apps, defect)

Description

[Anant Narayanan [:anant]]

Whenever AppCache detects that there is an update to its manifest, if the origin is associated with a known/installed web application, the OWA manifest for that application must also be updated.

If the name or icon of the web application was changed as a result of that OWA manifest update, the update must not be applied until the user confirms the change (in whatever way is convenient as determined by UX, most likely at a subsequent launch of the app by the user).

Comment 1

[nemo]

Is this bug why my attempt to follow:
https://developer.mozilla.org/en-US/docs/HTML/Using_the_application_cache#Example_1.3A_a_simple_cache_manifest_file

Completely failed?
As in, a file listed in the manifest did not update when cache.manifest was changed, even the file was touched on the server?

I wasn't able to get the file to refresh until I add ?randomstuff to the remote URL.

Kind of annoying, since it makes new releases a pain.

Comment 2

[nemo]

So, FWIW, my problem seems to have been addressed by ensuring manifest files are always cached.
That is:
ExpiresByType text/cache-manifest "access plus 0 seconds"

I experimented with a nocache header on everything else (which does *not* override the manifest, but I figured might be an issue if the manifest changed but the browser felt the local copy was recent enough)
<Files *>
Header set Cache-Control: "private, pre-check=0, post-check=0, max-age=0"
Header set Expires: 0
Header set Pragma: no-cache
</Files>

But that was *not* necessary.  Refreshing was sufficient to get a new copy so long as the manifest was expired.

Just passing this on in case your problem was the same.

Comment 3

[nemo]

Er. Sorry. By ensuring manifest files are *NOT* cached...

Comment 4

[Honza Bambas (:mayhemer)]

Cache-control: no-cache is what you want.  Firefox behaves by the spec here, but you are not the first one who complains (but actually, you are responsible to set the caching headers correctly on the server ;)).

This seems to be something we should propose to change in the Offline App Cache spec.

Comment 5

[Sylvestre Ledru [:Sylvestre]]

Core Graveyard / DOM: Apps is inactive. Closing all bugs in this component.