Bug 143070 - [WK2][NetworkCache] Compute if a cached response has expired only when actually needed
Summary: [WK2][NetworkCache] Compute if a cached response has expired only when actual...
Status: RESOLVED FIXED
Alias: None
Product: WebKit
Classification: Unclassified
Component: WebKit2 (show other bugs)
Version: 528+ (Nightly build)
Hardware: Unspecified Unspecified
: P2 Normal
Assignee: Chris Dumez
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-03-25 20:18 PDT by Chris Dumez
Modified: 2015-03-26 09:22 PDT (History)
2 users (show)

See Also:

Attachments
Patch (3.86 KB, patch)
2015-03-25 20:21 PDT, Chris Dumez 		no flags Details | Formatted Diff | Diff
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Chris Dumez 2015-03-25 20:18:58 PDT 
Compute if a cached response has expired only when actually needed:
- This is not a history navigation
and
- It does not have "Cache-Control: no-cache" header

Currently, we determine if the response has expired unconditionally and we often end up not using this information.
Comment 1 Chris Dumez 2015-03-25 20:21:07 PDT 
Created attachment 249467 [details]
Patch
Comment 2 WebKit Commit Bot 2015-03-26 09:22:28 PDT 
Comment on attachment 249467 [details]
Patch

Clearing flags on attachment: 249467

Committed r182010: <http://trac.webkit.org/changeset/182010>
Comment 3 WebKit Commit Bot 2015-03-26 09:22:33 PDT 
All reviewed patches have been landed.  Closing bug.