HTML5 Cache manifest file itself is not cached, and called at each resource load

Posted by Mic on Stack Overflow See other posts from Stack Overflow or by Mic
Published on 2010-03-09T20:56:21Z Indexed on 2010/03/12 6:57 UTC
Read the original article Hit count: 401

Filed under:
|
|
|
|

We have a web app that runs on the iPhone.
The manifest file is ok, and the resources(html, css, js) are cached correctly.
The page sits in the home screen.

The trouble is, when the page loads a resource from the cache, there is as well a GET call to the server to read the Cache Manifest file.
The server is configured to send the correct header (max-age=31536000; public, etc...) and caches well all other files except the cache manifest itself.

Is this a normal behavior? It looks there is a slight lag, because of that call, for each resource load.
Any idea, if these multiple calls can get a status 304 or even better avoided?

© Stack Overflow or respective owner

Related posts about JavaScript

Related posts about html5