- From: Andrew Betts <andrew.betts@ft.com>
- Date: Wed, 10 Oct 2012 09:18:42 +0100
- To: Michael Nordman <michaeln@google.com>
- Cc: Patrick Gillespie <patorjk@gmail.com>, Jake Archibald <jaffathecake@gmail.com>, Chris Wilson <cwilso@google.com>, public-fixing-appcache@w3.org
> ... but that mechanism does not currently apply to cross-origin 3xx redirect responses. Cross-origin 3xx redirects should always trigger the fallback behavior. > > This was added to chrome to support a use case where an error response was expected while online in the context of Google Docs. An attempt to do something with a 'doc' that had been deleted or whose permissions had changed such that the current user had no access would result in an error response that should be shown to the user. The default fallback behavior was getting in the way of that. > > This half-measure with the extra header got us out of a bind, but it's not very satisfying as a general solution. How do you deal with this use case in browsers other than Chrome? I'm wondering if there an adequate workaround for developers who don't have the luxury of being able to patch the browser, or whether this should be considered a failing of appcache for which there is currently no adequate remedy. Andrew -- ------------------------------ This email was sent by a company owned by Pearson plc, registered office at 80 Strand, London WC2R 0RL. Registered in England and Wales with company number 53723.
Received on Wednesday, 10 October 2012 09:34:08 UTC