Reporting API
The securitypolicyviolation event is fired when a Content Security Policy is violated.
The event is fired on the element when there is a violation of the CSP policy.
This event bubbles to the Window object, and is composed.
[!NOTE] You should generally add the handler for this event to a top-level object (i.e., Window or Document). While HTML elements can technically be the target of the
securitypolicyviolationevent, in reality this event does not fire on them—for example, a blocked<img>source directly triggers this event ondocumentas the target, instead of bubbling from the<img>element.
Syntax
Use the event name in EventTarget/addEventListener:
addEventListener("securitypolicyviolation", (event) => { })
Alternatively, assign to the event handler property of the interface:
onsecuritypolicyviolation = (event) => { }
Event type
A SecurityPolicyViolationEvent. Inherits from Event.
SecurityPolicyViolationEvent
Examples
Listening for securitypolicyviolation on Window
The code below shows how you might add an event handler function using the onsecuritypolicyviolation global event handler property (but note that this replaces other event listeners added using onsecuritypolicyviolation, if any) or addEventListener() on the top level Window (you could use exactly the same approach on Document).
window.onsecuritypolicyviolation = (e) => {
// Handle SecurityPolicyViolationEvent e here
};
window.addEventListener("securitypolicyviolation", (e) => {
// Handle SecurityPolicyViolationEvent e here
});
Specifications
Browser compatibility
See also
- The Document/securitypolicyviolation_event event of the Document interface
- The WorkerGlobalScope/securitypolicyviolation_event event of the WorkerGlobalScope interface
- HTTP > Content Security Policy
来源:MDN Web Docs / Mozilla 贡献者 · 作者与贡献记录 · CC BY-SA 2.5。离线整理了版式、链接和媒体显示。
