Bug 167497

Summary: Implement Cache-control: immutable
Product: WebKit Reporter: Antti Koivisto <koivisto>
Component: Page LoadingAssignee: Nobody <webkit-unassigned>
Status: RESOLVED FIXED    
Severity: Normal CC: 7raivis, beidson, cdumez, commit-queue, dbates, japhet, mathias, m.kurz+webkitbugs
Priority: P2    
Version: WebKit Nightly Build   
Hardware: Unspecified   
OS: Unspecified   
Attachments:
Description Flags
patch none

Description Antti Koivisto 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/
Comment 1 Antti Koivisto 2017-01-27 06:50:20 PST 
Created attachment 299930 [details]
patch
Comment 2 Chris Dumez 2017-01-27 09:15:40 PST 
Comment on attachment 299930 [details]
patch

r=me
Comment 3 Antti Koivisto 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.
Comment 4 Chris Dumez 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
Comment 5 Antti Koivisto 2017-01-27 10:35:57 PST 
<rdar://problem/30236250>
Comment 6 WebKit Commit Bot 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>
Comment 7 WebKit Commit Bot 2017-01-27 10:45:45 PST 
All reviewed patches have been landed.  Closing bug.