[html5] app manifest & 404/500 pages

[Josh Sharpe]

> I don't see the problem. You should presumably never be sending back a
> 404, since the user will never request a page you don't have unless you
> have a broken link or something, and you should never ever send back a 500
> unless your server is in fact offline (or broken, which amounts to the
> same thing).
>

Yes, of course the app shouldn't be making a habit out of returning 404 and
500 pages.  That doesn't mean it won't ever happen and shouldn't
be accommodated for.  Pages get removed, google has stale links, other
sites have link backs, users type the wrong thing into the URL bar....


> Generally speaking, by the way, having your entire site in the FALLBACK
> section under one entry is probably not what you want. The FALLBACK
> section is supposed to just be for files that you would want to have
> cached but that you don't cache because there's too many of them (e.g.
> photos on Flickr). The fallback page is supposed to be able to generate
> the page from the local database, if the data is available.
>

I'm using a derivative of an example given by current living standard.

See section 6.3.3.1 (last example)
http://www.whatwg.org/specs/web-apps/current-work/multipage/offline.html#some-sample-manifests

... as far as I can tell that example is going to break all existing error
pages and is probably not something that should be in the standard unless
there's a workaround for the issue.



> --
> Ian Hickson               U+1047E                )\._.,--....,'``.    fL
> http://ln.hixie.ch/       U+263A                /,   _.. \   _\  ;`._ ,.
> Things that are impossible just take longer.   `._.-(,_..'--(,_..'`-.;.'
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.whatwg.org/pipermail/help-whatwg.org/attachments/20120211/a7968631/attachment-0002.htm>