Cache-control value 'immutable' indicates that a subresource does not change and so does not need to be revalidated on a normal reload. This can significantly speed up reloads and reduce network traffic. It is has been implemented in Firefox and is already used by Facebook. https://tools.ietf.org/html/draft-mcmanus-immutable-00 https://hacks.mozilla.org/2017/01/using-immutable-caching-to-speed-up-the-web/
Created attachment 299930 [details] patch
Comment on attachment 299930 [details] patch r=me
We may want to implement Chrome-style reload behavior where non-expired subresources with explicit cache lifetime are never revalidated. This would make 'immutable' support unnecessary. Meanwhile, lets try this.
(In reply to comment #3) > We may want to implement Chrome-style reload behavior where non-expired > subresources with explicit cache lifetime are never revalidated. This would > make 'immutable' support unnecessary. Meanwhile, lets try this. Agreed
<rdar://problem/30236250>
Comment on attachment 299930 [details] patch Clearing flags on attachment: 299930 Committed r211288: <http://trac.webkit.org/changeset/211288>
All reviewed patches have been landed. Closing bug.