<br>Hi Ian, <br><br>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".<br>
<br>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?<br>
<br>Rik.<br><br><br><br><br clear="all">Rik Sagar, San Jose, CA 95124<br>Visit : <a href="http://sagar.org/" target="_blank">http://sagar.org/</a><br> <br> <a href="tel:%2B1-408-799-4589" value="+14087994589" target="_blank">+1-408-799-4589</a> (mobile)<br>
0113-815-1583 (from UK)<br>
<br><br><div class="gmail_quote">On Sat, Feb 11, 2012 at 12:20 PM, Josh Sharpe <span dir="ltr"><<a href="mailto:josh.m.sharpe@gmail.com" target="_blank">josh.m.sharpe@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class="gmail_quote"><div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">I don't see the problem. You should presumably never be sending back a<br>
404, since the user will never request a page you don't have unless you<br>
have a broken link or something, and you should never ever send back a 500<br>
unless your server is in fact offline (or broken, which amounts to the<br>
same thing).<br></blockquote><div><br></div></div><div>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.... </div>
<div>
<div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Generally speaking, by the way, having your entire site in the FALLBACK<br>
section under one entry is probably not what you want. The FALLBACK<br>
section is supposed to just be for files that you would want to have<br>
cached but that you don't cache because there's too many of them (e.g.<br>
photos on Flickr). The fallback page is supposed to be able to generate<br>
the page from the local database, if the data is available.<br></blockquote><div><br></div></div><div>I'm using a derivative of an example given by current living standard.</div><div><br></div><div>See section 6.3.3.1 (last example)</div>
<div><a href="http://www.whatwg.org/specs/web-apps/current-work/multipage/offline.html#some-sample-manifests" target="_blank">http://www.whatwg.org/specs/web-apps/current-work/multipage/offline.html#some-sample-manifests</a></div>
<div><br>
</div><div>... 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.</div><div>
<div><br></div>
<div>
<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div><div><br>
--<br>
Ian Hickson U+1047E )\._.,--....,'``. fL<br>
<a href="http://ln.hixie.ch/" target="_blank">http://ln.hixie.ch/</a> U+263A /, _.. \ _\ ;`._ ,.<br>
Things that are impossible just take longer. `._.-(,_..'--(,_..'`-.;.'<br>
</div></div></blockquote></div></div><br>
<br>_______________________________________________<br>
Help mailing list<br>
<a href="mailto:Help@lists.whatwg.org" target="_blank">Help@lists.whatwg.org</a><br>
<a href="http://lists.whatwg.org/listinfo.cgi/help-whatwg.org" target="_blank">http://lists.whatwg.org/listinfo.cgi/help-whatwg.org</a><br>
<br></blockquote></div><br>