Closed
Bug 968606
Opened 10 years ago
Closed 10 years ago
HTTP cache v2: audit old cache usage
Categories
(Core :: Networking: Cache, defect)
Tracking
()
RESOLVED
FIXED
mozilla30
People
(Reporter: mayhemer, Assigned: mayhemer)
References
Details
Attachments
(1 file, 1 obsolete file)
1.07 KB,
patch
|
bbondy
:
review+
|
Details | Diff | Splinter Review |
No new found, but one forgotten: http://mxr.mozilla.org/mozilla-central/source/browser/components/preferences/in-content/advanced.js#404
Assignee | ||
Comment 1•10 years ago
|
||
One place I found where the new HTTP cache API is not used yet.
Comment 2•10 years ago
|
||
Comment on attachment 8373541 [details] [diff] [review] v1 Review of attachment 8373541 [details] [diff] [review]: ----------------------------------------------------------------- ::: browser/components/preferences/in-content/advanced.js @@ +400,5 @@ > * Clears the cache. > */ > clearCache: function () > { > + Services.cache2.clear(); This file should stay in sync with advanced.js. Did something change in advanced.js recentlyt hat's not reflected in dxr? http://dxr.mozilla.org/mozilla-central/source/browser/components/preferences/advanced.js#414
Attachment #8373541 -
Flags: review?(netzen)
Assignee | ||
Comment 3•10 years ago
|
||
I'm not sure I follow - you want the code be same? Like: don't use Services and leave the {try catch}?
Comment 4•10 years ago
|
||
The code in in content preferences should match the code in normal preferences. If you want to make this change, then it should be done in both places and not only one place.
Assignee | ||
Comment 5•10 years ago
|
||
Got it. New patch will come. Thanks.
Assignee | ||
Comment 6•10 years ago
|
||
Attachment #8373541 -
Attachment is obsolete: true
Attachment #8375945 -
Flags: review?(netzen)
Updated•10 years ago
|
Attachment #8375945 -
Flags: review?(netzen) → review+
Comment 7•10 years ago
|
||
https://hg.mozilla.org/mozilla-central/rev/7ec73b94e194
Status: ASSIGNED → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla30
You need to log in
before you can comment on or make changes to this bug.
Description
•