Open
Bug 1214360
Opened 9 years ago
Updated 2 years ago
"clear-origin-data" in HTTP cache doesn't do pattern matching
Categories
(Core :: Networking: Cache, defect, P3)
Core
Networking: Cache
Tracking
()
NEW
| Tracking | Status | |
|---|---|---|
| firefox44 | --- | affected |
People
(Reporter: mayhemer, Unassigned)
References
Details
(Whiteboard: [necko-backlog])
See bug 1165269 comment 47.
Apparently we need to do a pattern matching, similar to what I do for localStorage in https://bugzilla.mozilla.org/show_bug.cgi?id=1165214#c88
Michal, the index iterators need to do matching against a pattern we obtain in "clear-origin-data". How complicated would it be based on top of bug 1201042?
Also I'm concerned about the patch for that bug, since it stores the OriginAttributes incompletely, so that the match functionality actually cannot be properly implemented.
Flags: needinfo?(michal.novotny)
|
||
Updated•9 years ago
|
Whiteboard: [necko-backlog]
|
||
Comment 2•7 years ago
|
||
Bulk change to priority: https://bugzilla.mozilla.org/show_bug.cgi?id=1399258
Priority: -- → P1
|
|
||
Comment 3•7 years ago
|
||
Bulk change to priority: https://bugzilla.mozilla.org/show_bug.cgi?id=1399258
Priority: P1 → P3
|
||
Updated•2 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•