- From: Mark Nottingham <mnot@mnot.net>
- Date: Thu, 14 Mar 2024 14:11:33 +1100
- To: Jeremy Roman <jbroman@chromium.org>
- Cc: ietf-http-wg@w3.org
Personally, I'm supportive, but that's probably not surprising :) > On 21 Feb 2024, at 13:08, Jeremy Roman <jbroman@chromium.org> wrote: > > Hello HTTPWG: > > I'm working on speculative loading in Google Chrome (most saliently, prefetch of documents for navigation) and looking at ways to address the potential problem of prefetched resources becoming "stale" by the time they are used due to the user logging in or out (or similar state changes), in response to developer feedback. Workarounds are possible but somewhat awkward. > > Fundamentally it seems like something less strict than "Vary: Cookie" is called for, which would let the client know which cookie values, if changed, invalidate the cached resource. The semantics of this seem potentially useful for other kinds of cache (e.g., some caching proxies can be configured to work this way), so HTTP WG seems like potentially the right venue to discuss this. > > Mark Nottingham's Cookie-Indices proposal (part of HTTP Availability Hints) seems likely to address the problem and ought to be implementable (I'm prototyping it in Chromium's prefetch cache, at least), so that's what I'm looking at right now, but at this moment we're not yet committed to a particular solution. > > What do you all think? -- Mark Nottingham https://www.mnot.net/
Received on Thursday, 14 March 2024 03:11:40 UTC