This type of request (see forwarded message below) to utilize the
application cache for subresource loads into documents that are not stored
in the cache has come up several times now. The current feature set is very
focused on the "offline" use case. Is it worth making additions such that a
document that loads from a server can utilize the resources in an appcache?

Today we have <html manifest="manifestFile">, which adds the document
containing this tag to the appcache and associates that doc with that
appcache such that subresource loads hit the appcache.

Not a complete proposal, but...

What if we had something along the lines of <html
useManifest=''manifestFile">, which would do the association of the doc with
the appcache (so subresources loads hit the cache) but not add the document
to the cache?

---------- Forwarded message ----------
From: UVL <>
Date: Sun, Dec 19, 2010 at 1:35 PM
Subject: [chromium-html5] Application Cache for on-line sites
To: Chromium HTML5 <>

I tried to use the HTML5 Application Cache to improve the performances
of on-line sites (all the tutorials on the web write only about usage
with off-line apps)

I created the manifest listing all the js, css and images, and the
performances were really exciting, until I found that even the page
HTML was cached, despite it was not listed in the manifest. The pages
of the site are in PHP, so I don't want them to be cached.

"Authors are encouraged to include the main page in the manifest also,
but in practice the page that referenced the manifest is automatically
cached even if it isn't explicitly mentioned."

Is there a way to have this automating caching disabled?

Note: I know that caching can be controlled via HTTP headers, but I
just wanted to try this way as it looks quite reliable, clean and

You received this message because you are subscribed to the Google Groups
"Chromium HTML5" group.
To post to this group, send email to
To unsubscribe from this group, send email to<>
For more options, visit this group at

Reply via email to