Bug 68154

Summary: Chrome: webRequest.onBeforeRequest doesn't fire for results loaded from the cache (MemoryCache?)
Product: WebKit Reporter: Dominic Battre <battre>
Component: WebKit Misc.Assignee: Nobody <webkit-unassigned>
Status: UNCONFIRMED    
Severity: Normal CC: abarth, fishd
Priority: P2    
Version: 528+ (Nightly build)   
Hardware: Unspecified   
OS: Unspecified   
URL: http://crbug.com/94284
Attachments:
Description Flags
Patch
none
Patch fishd: review-

Dominic Battre
Reported 2011-09-15 05:39:23 PDT
This is a companion bug for http://crbug.com/94284
Attachments
Patch (3.60 KB, patch)
2011-09-15 05:55 PDT, Dominic Battre 		no flags
DetailsFormatted DiffDiff
Patch (3.80 KB, patch)
2011-09-16 04:44 PDT, Dominic Battre 		fishd: review-
DetailsFormatted DiffDiff
Show Obsolete (1) View All Add attachment proposed patch, testcase, etc.
Dominic Battre
Comment 1 2011-09-15 05:55:57 PDT
Created attachment 107480 [details] Patch
Dominic Battre
Comment 2 2011-09-16 04:44:14 PDT
Created attachment 107635 [details] Patch
Darin Fisher (:fishd, Google)
Comment 3 2011-09-16 22:37:44 PDT
Why is clearing the cache the answer? It seems like you should instead observe cache reads.
Adam Barth
Comment 4 2011-09-16 22:40:28 PDT
> Why is clearing the cache the answer? It seems like you should instead observe cache reads. There's some discussion of this in the Chromium bug. One of the constraints is that we need to answer questions about the cache synchronously in order to get reasonable performance / user experience. I don't think we've found any great solutions to all the constraints.
Darin Fisher (:fishd, Google)
Comment 5 2011-09-16 22:41:52 PDT
Comment on attachment 107635 [details] Patch View in context: https://bugs.webkit.org/attachment.cgi?id=107635&action=review > Source/WebKit/chromium/public/WebCache.h:80 > + WEBKIT_EXPORT static void requestDelayedClear(); also, there's no good reason to have this 'delayed clear' state in webkit. if you need that, it could be held by the embedder.
Note You need to log in before you can comment on or make changes to this bug.