On Wed, Aug 24, 2016 at 10:17 AM, Roy T. Fielding <fielding@gbiv.com> wrote: > > FWIW, the mistake above is in saying "response is stale … it will need to > be revalidated". > > An HTTP client is not required to revalidate a stale response. It only > needs to do so when > ensuring semantic transparency, which is something that user agents > frequently don't do > within the scope of a single session (instead, they make requests based on > configuration > or on the state of their own request processing). > Out of curiosity, can you walk through how you arrived at that interpretation for this specific case? Are you essentially suggesting that the "push store" (or "side cache") should be treated more like a history list (RFC 7234, Section 6) rather than a true HTTP cache?
Received on Wednesday, 24 August 2016 18:24:21 UTC