RE: Call for Adoption -- Cache-Control: immutable

I'm generally favorable toward this idea, but will note one open question in my mind:  This seems to be very tightly tied to the scenario of hitting refresh on a page whose content frequently changes but whose dependent resources don't.  Putting "immutable" on those dependent resources helps reduce the server load and time taken when the user hits refresh, either in their own local cache or in proxies that are on path to the site.

There seems to be a parallel discussion (see for Chrome's) about softening the behavior of the refresh button to avoid force-refreshing all dependencies, which would likely have the same results.  Can someone point me to a scenario in which both are worth doing, or is this really a pair of mutually-sufficient solutions to the same problem?

-----Original Message-----
From: Mark Nottingham [] 
Sent: Wednesday, December 7, 2016 8:04 PM
To: HTTP Working Group <>
Cc: Patrick McManus <>
Subject: Call for Adoption -- Cache-Control: immutable

As discussed in Seoul, there seems to be strong interest in adopting Patrick's draft:

Please indicate any concerns on-list; statements of support would also be helpful.


Mark Nottingham

Received on Thursday, 8 December 2016 04:56:21 UTC