Subject: [httpwg/http-extensions] The inverse of immutable (#288)

From: HTTP issue updates <[email-masked]>
Date: Thu, 02 Feb 2017 18:17:11 -0800

Chrome currently implements the semantics of `immutable` using a browser heuristic rather than an explicit signal from the server.

if we define a complimentary CC extension with the inverse semantics of `immutable` -- i.e., roughly, "always refresh this when the user hits reload" -- it would allow Chrome to continue using a heuristic, but override it with an explicit signal from the server when the server cares about it.

If we do that, I think the CC extension name should be short (e.g., one or two characters).

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/httpwg/http-extensions/issues/288