Bug 143070

Summary: [WK2][NetworkCache] Compute if a cached response has expired only when actually needed
Product: WebKit Reporter: Chris Dumez <cdumez>
Component: WebKit2Assignee: Chris Dumez <cdumez>
Status: RESOLVED FIXED    
Severity: Normal CC: commit-queue, koivisto
Priority: P2    
Version: 528+ (Nightly build)   
Hardware: Unspecified   
OS: Unspecified   
Attachments:
Description Flags
Patch none

Chris Dumez
Reported 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.
Attachments
Patch (3.86 KB, patch)
2015-03-25 20:21 PDT, Chris Dumez 		no flags
DetailsFormatted DiffDiff
View All Add attachment proposed patch, testcase, etc.
Chris Dumez
Comment 1 2015-03-25 20:21:07 PDT
Created attachment 249467 [details] Patch
WebKit Commit Bot
Comment 2 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>
WebKit Commit Bot
Comment 3 2015-03-26 09:22:33 PDT
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.