[html5] app manifest & 404/500 pages

[Josh Sharpe]

Any thoughts on a work around for this?  Right now I think I'm stuck with
making my error pages return status codes of 200.

On Mon, Feb 13, 2012 at 8:35 PM, Rik Sagar <org.whatwg at sagar.org> wrote:

>
> Hi Ian,
>
> I'm don't see the "rarely offline" notion as a good argument for the
> behavior described.  IMHO if a server is responding with an error it's not
> appropriate for the client to interpret that as "I'm offline".
>
> I also don't think the captive portal argument is valid.  If I hit a
> captive portal I don't get an error, I get a splash page with a login
> button.  I'm not sure if I get a 3xx page first, I imagine I should.  And
> in that case, I really need to see that page (rather than cached copy of
> the real site).  Otherwise how will I accept the portals TOS and get
> connected to the Internet?
>
> Rik.
>
>
>
>
> Rik Sagar, San Jose, CA 95124
> Visit : http://sagar.org/
>
>   +1-408-799-4589  (mobile)
>   0113-815-1583 (from UK)
>
>
> On Sat, Feb 11, 2012 at 12:20 PM, Josh Sharpe <josh.m.sharpe at gmail.com>wrote:
>
>>
>>
>>> 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.   `._.-(,_..'--(,_..'`-.;.'
>>>
>>
>>
>> _______________________________________________
>> Help mailing list
>> Help at lists.whatwg.org
>> http://lists.whatwg.org/listinfo.cgi/help-whatwg.org
>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.whatwg.org/pipermail/help-whatwg.org/attachments/20120216/7441a8fa/attachment-0002.htm>