It'd be loads better if application logic were directly responsible for making these sort of policy decisions regarding what cached resource to use under what circumstance. Obscure least-common-denominator rules baked into the user agent with even more obscure ways to override that least-common-denominator behavior just isn't working out very well.
> In my opinion the UA should *always* use server returned... And in some other developers opinion, that would defeat efforts to make the client resilient to 5xx errors. On Thu, Dec 20, 2012 at 2:24 AM, Mikko Rantalainen < mikko.rantalai...@peda.net> wrote: > connect the server and > gets HTTP 410 Gone, I'd be pretty upset if cached offline copy would be > used automatically. The server has clearly responded that the requested > document is intentionally removed. End user seeing cached (stale) copy > instead is very far from intented result in this case. >
