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

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 bett开发者_运维知识库er avoided?

you should check the spec for details, but it would be logical for the manifest file to be regularly checked for updates (every session, or every hour or ...) and for it not to follow http-header-cache directives, but it would not be logical if that would happen on each and every request for a file in cache.

so this might actually be a bug in your code or in mobile safari?

the spec mentions support for a http 304 response code, so making sure that is send might indeed be a solution.