RESOLVED FIXED 167497
Implement Cache-control: immutable 
https://bugs.webkit.org/show_bug.cgi?id=167497
Summary Implement Cache-control: immutable
Antti Koivisto
Reported 2017-01-27 03:56:07 PST
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/
Attachments
patch (11.54 KB, patch)
2017-01-27 06:50 PST, Antti Koivisto 		no flags
DetailsFormatted DiffDiff
View All Add attachment proposed patch, testcase, etc.
Antti Koivisto
Comment 1 2017-01-27 06:50:20 PST
Created attachment 299930 [details] patch
Chris Dumez
Comment 2 2017-01-27 09:15:40 PST
Comment on attachment 299930 [details] patch r=me
Antti Koivisto
Comment 3 2017-01-27 10:20:16 PST
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.
Chris Dumez
Comment 4 2017-01-27 10:21:04 PST
(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
Antti Koivisto
Comment 5 2017-01-27 10:35:57 PST
<rdar://problem/30236250>
WebKit Commit Bot
Comment 6 2017-01-27 10:45:39 PST
Comment on attachment 299930 [details] patch Clearing flags on attachment: 299930 Committed r211288: <http://trac.webkit.org/changeset/211288>
WebKit Commit Bot
Comment 7 2017-01-27 10:45:45 PST
All reviewed patches have been landed. Closing bug.
Note You need to log in before you can comment on or make changes to this bug.