[html5] app manifest & 404/500 pages
josh.m.sharpe at gmail.com
Wed Feb 8 13:20:35 PST 2012
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
2) Don't use the FALLBACK directive with "/ /foo"
Maybe there's some workaround?
Btw, the FALLBACK example that I'm using is basically the last one
On Wed, Feb 8, 2012 at 3:30 PM, Ian Hickson <ian at hixie.ch> wrote:
> On Tue, 7 Feb 2012, Josh Sharpe wrote:
> > I have a manifest that looks somethin like this:
> > CACHE MANIFEST
> > # e4a75fb378cb627a0d51a80c1cc5684c2d918d93e267f5854a511aa3c8db5b1a
> > /a/application.js
> > /a/application.css
> > NETWORK:
> > *
> > FALLBACK:
> > / /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
> > the fallback. They both act just as if the server is offline.
> This is intentional. A server responding with an error code or redirect is
> how we determine whether the server is offline or not.
> (In practice, people are rarely "offline", so much as just in a very bad
> network situation or on wifi with a captive portal, where all traffic to
> your site gets redirected. That's why we use this mechanism.)
> 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...
More information about the Help