0

I may get some heat for this question because there are a lot out there already.

BUT... Every question has a different answer and no finite answer seems to be solid.

SO THE QUESTION... If I update a file which is reference in the application cache manifest for an offline available application, how can i force the update of the manifest and the offline cache without changing the manifest?

I hope this is clear. To show that I have done some research:

How to properly invalidate an HTML5 Cache Manifest for online/offline web apps?

https://stackoverflow.com/a/8211563/491044

Updating the cache This requires a change to the manifest though...

Thank you all.

Improve this question

1 Answer 1

Reset to default
2

You can't. You must update the manifest file. Be careful to set an immediate expiry header on your manifest file so that the browser recognizes there's been an update to it.

Improve this answer
Sign up to request clarification or add additional context in comments.

4 Comments

Most posts I have read seem to insist that the browsers (Opera and FF) ignore the expiry date. This seems to easy a solution for a topic which has so many Q&As. I will try it myself as I have not yet. Thanks for the answer.
@trgraglia Check out the expiry settings in HTML5 Boilerplate.
That combined with a datetime and version comment update in the manifest seems to do the trick. Thank you.
I'm convinced there is still something else that is missing. I update the manifest every time a file in it changes, and apache emits the proper headers to prevent caching, yet intermittently Firefox refuses the load the updated file even after looking at the new manifest.

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.