[html5] app manifest & 404/500 pages

[Josh Sharpe]

None of this solves the problem at hand though....

To restate it:

My manifest has an OFFLINE section of "/ /offline"

Once that manifest has been loaded, and cached successfully and the user is
still online, my 404 and 500 pages are broken.  Instead of showing the
content of those pages, the browser is rendering the cached version of
/offline

The only solution I can figure out right now is to have those pages respond
with 200, which is just wrong.

I'm sorry if I've missed your proposed solution.  Would you mind
elaborating once more?

Thanks!
Josh

On Wed, Feb 8, 2012 at 4:29 PM, Ian Hickson <ian at hixie.ch> wrote:

> On Wed, 8 Feb 2012, Josh Sharpe wrote:
> >
> > There must be some altnative or a best-practice that I'm missing here.
> >
> > Based on your response I can only conclude that I either
> > 1) Don't respond, ever, with 400+ error codes
>
> You can respond with 4xx and 5xx codes, sure. This should never be an
> issue. You'll only ever respond with a 4xx code in the case of a
> client-side error, which should never happen, and you'll only ever respond
> with 5xx codes in the case of a server-side error, in which case you might
> as well be offline.
>
> --
> 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/20120210/4365aec6/attachment-0002.htm>