Content-Security-Policy: script-src-attr directive


目录

The HTTP Content-Security-Policy (CSP) script-src-attr directive specifies valid sources for JavaScript inline event handlers.

This directive only specifies valid sources for inline script event handlers like onclick. It does not apply to other JavaScript sources that can trigger script execution, such as URLs loaded directly into script elements and XSLT stylesheets. (Valid sources can be specified for all JavaScript script sources using script-src, or just for <script> elements using script-src-elem.)

CSP version 3
Directive type [Fetch directive](https://developer.mozilla.org/en-US/docs/Glossary/Fetch%20directive)
[default-src](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Content-Security-Policy/default-src) fallback Yes. If this directive is absent, the user agent will look for the [script-src](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Content-Security-Policy/script-src) directive, and if both of them are absent, fallback to default-src directive.

Syntax

Content-Security-Policy: script-src-attr 'none';
Content-Security-Policy: script-src-attr <source-expression-list>;

This directive may have one of the following values:

script-src-attr can be used in conjunction with script-src, and will override that directive for checks on inline handlers:

Content-Security-Policy: script-src <source>;
Content-Security-Policy: script-src-attr <source>;

Examples

Violation case

Given this CSP header:

Content-Security-Policy: script-src-attr 'none'

…the following inline event handler is blocked and won't be loaded or executed:

<button id="btn" onclick="doSomething()">Click me</button>

Note that generally you should replace inline event handlers with addEventListener calls:

document.getElementById("btn").addEventListener("click", doSomething);

Specifications

Browser compatibility

See also


版本号 #3
由 壳壳虫 创建于 2026-10-31 03:27:53 UTC
由 cocobook-sync 更新于 2026-11-04 17:35:43 UTC