Re: [quicwg/base-drafts] Push and Cache Interaction (#3530)

["Roy T. Fielding" <[e-mail]>]

My comment was intended to be editorial for QUIC, but it is also critical to understand from an implementation perspective (regardless of protocol).

When a browser makes a request and receives a 2xx response, that response is not "part of the cache". It is part of the working state (hypertext workspace) for the user agent (windows/tabs/history). The response may also be cached, but the working state is not subject to cache controls or freshness. The same should be true for push or it won't be usable for non-cached session-specific content.

I don't need QUIC to redefine that. It's actually something that should be defined by user agents (Fetch). What I need is for the HTTP/3 text to be consistent with the existing distinction between the working state of a user agent and the terminology for a cache. They are distinct on purpose. We should probably reinforce that in http-core as well, beyond the brief section in Caching.

I'd prefer that we keep this open (editorial) until I get a chance to review the next draft version.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/quicwg/base-drafts/issues/3530#issuecomment-601306624