- From: Ian Hickson <ian@hixie.ch>
- Date: Mon, 17 Dec 2012 21:30:06 +0000 (UTC)
- To: David Barrett-Kahn <dbk@google.com>
- Cc: whatwg@whatwg.org, Josh Sharpe <josh.m.sharpe@gmail.com>
On Tue, 11 Dec 2012, David Barrett-Kahn wrote: > > We ran into this same problem on Google Docs offline. Our solution was > to add a proprietary response header to Chrome which instructs the > browser that the response is not to trigger the fallback entry, despite > its response code. Something like it could be considered for > standardization. I know there are some people on the Chrome team looking > to advance some new appcache features, and that this use case is on > their list. Can you elaborate on the need for this feature? Why would you ever send the user to a 404 page intentionally (i.e. when the server isn't broken)? Similarly, why would you not consider the server returning 500 a good indication that the cache should be used? -- Ian Hickson U+1047E )\._.,--....,'``. fL http://ln.hixie.ch/ U+263A /, _.. \ _\ ;`._ ,. Things that are impossible just take longer. `._.-(,_..'--(,_..'`-.;.'
Received on Monday, 17 December 2012 21:30:32 UTC