[html5] app manifest & 404/500 pages

Josh Sharpe josh.m.sharpe at gmail.com
Tue Feb 7 18:21:06 PST 2012

I have a manifest that looks somethin like this:

# e4a75fb378cb627a0d51a80c1cc5684c2d918d93e267f5854a511aa3c8db5b1a


/ /offline

The issue is that my /404.html and /500.html pages (that
are obviously served up with a response code of 404 and 500) are triggering
the fallback.  They both act just as if the server is offline.

My question is twofold:

1) Why does /404.html trigger the fallback when /events doesn't?
2) How can I allow /404.html and /500.html to not trigger the fallback
while still allowing / to trigger it.

For what it's worth, I've already tried this:


... however since those pages are served w/ a non-200 response code, it
triggers the app cache error callback and the cache isn't saved.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.whatwg.org/pipermail/help-whatwg.org/attachments/20120207/c00732d9/attachment-0001.htm>

More information about the Help mailing list