Closed
Bug 1028724
Opened 10 years ago
Closed 8 years ago
nsPrincipal: no CSP object for a Chrome page
Categories
(Core :: DOM: Security, defect)
Tracking
()
RESOLVED
DUPLICATE
of bug 1224694
People
(Reporter: nicolas, Unassigned)
Details
(Whiteboard: [domsecurity-backlog])
User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:29.0) Gecko/20100101 Firefox/29.0 (Beta/Release) Build ID: 20140503045623 Steps to reproduce: Tried to add some code to apply a CSP to chrome pages. (For testing patches for https://bugzilla.mozilla.org/show_bug.cgi?id=948900) Actual results: Got a NULL pointer from `principal->GetCsp()`. Also, got `NS_OK`, see https://bugzilla.mozilla.org/show_bug.cgi?id=1028721 Expected results: Getting a useable CSP object.
Comment 1•10 years ago
|
||
There's only a CSP if there is an actual policy applied...
Component: Security: CAPS → Security
Comment 2•8 years ago
|
||
Within Bug 1224694 we updated that functionality to 'principal->EnsureCSP()'. Marking this bug as a duplicate to add a reference.
Status: UNCONFIRMED → RESOLVED
Closed: 8 years ago
Component: Security → DOM: Security
Resolution: --- → DUPLICATE
Whiteboard: [domsecurity-backlog]
You need to log in
before you can comment on or make changes to this bug.
Description
•