Closed
Bug 1505203
Opened 7 years ago
Closed 7 years ago
Consider extending webRequest.resourceType to sync with fetch destinations
Categories
(WebExtensions :: Request Handling, enhancement, P5)
WebExtensions
Request Handling
Tracking
(Not tracked)
RESOLVED
DUPLICATE
of bug 1503898
People
(Reporter: April, Unassigned)
Details
(Whiteboard: [privacy])
I write a webExtension that is fairly widely used in the web security world to generate Content Security Policies. How it does this is by watching the webRequests that a site issues, looks at their details.documentUrl, details.url, and details.type, and maps that to a proper CSP report.
While this works for most things, it doesn't work for some things like workers, which would have a worker-src in CSP, but details.type has a type of "script".
It would be nice if either:
a) details.type (aka webRequest.ResourceType) would return what the fetch specification has for destination type ("worker"), or
b) details had an additional key (such as details.fetchType) that mapped to the fetch destination type
Thanks!
Updated•7 years ago
|
Severity: normal → enhancement
Whiteboard: [privacy]
Comment 1•7 years ago
|
||
April, this seems like an easy win, but I'm going to loop Shane in for an engineering perspective.
Flags: needinfo?(mixedpuppy)
Priority: -- → P5
Reporter | ||
Comment 2•7 years ago
|
||
I would add that I've figured out a workaround for my particular extension, but I still think this is the right (if low priority) thing to do and would benefit a number of other extensions.
Updated•7 years ago
|
Status: NEW → RESOLVED
Closed: 7 years ago
Flags: needinfo?(mixedpuppy)
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•