Content-Security-Policy
The HTTP Content-Security-Policy
response header allows
website administrators to control resources the user agent is allowed to load for a
given page. With a few exceptions, policies mostly involve specifying server origins and
script endpoints. This helps guard against cross-site scripting attacks
(Cross-site_scripting).
For more information, see the introductory article on Content Security Policy (CSP).
Header type | Response header |
---|---|
Forbidden header name | no |
Syntax
http
Content-Security-Policy: <policy-directive>; <policy-directive>
where <policy-directive>
consists of:
<directive> <value>
with no internal punctuation.
Directives
Fetch directives
Fetch directives control the locations from which certain resource types may be loaded.
child-src
-
Defines the valid sources for web workers and nested browsing contexts loaded using elements such as
<frame>
and<iframe>
.Warning: Instead of
child-src
, if you want to regulate nested browsing contexts and workers, you should use theframe-src
andworker-src
directives, respectively. connect-src
-
Restricts the URLs which can be loaded using script interfaces.
default-src
-
Serves as a fallback for the other fetch directives.
font-src
-
Specifies valid sources for fonts loaded using
@font-face
. frame-src
-
Specifies valid sources for nested browsing contexts loading using elements such as
<frame>
and<iframe>
. img-src
-
Specifies valid sources of images and favicons.
manifest-src
-
Specifies valid sources of application manifest files.
media-src
-
Specifies valid sources for loading media using the
<audio>
,<video>
and<track>
elements. object-src
-
Specifies valid sources for the
<object>
and<embed>
elements.Note: Elements controlled by
object-src
are perhaps coincidentally considered legacy HTML elements and are not receiving new standardized features (such as the security attributessandbox
orallow
for<iframe>
). Therefore it is recommended to restrict this fetch-directive (e.g., explicitly setobject-src 'none'
if possible). prefetch-src
Deprecated Non-standard-
Specifies valid sources to be prefetched or prerendered.
script-src
-
Specifies valid sources for JavaScript and WebAssembly resources.
script-src-elem
-
Specifies valid sources for JavaScript
<script>
elements. script-src-attr
-
Specifies valid sources for JavaScript inline event handlers.
style-src
-
Specifies valid sources for stylesheets.
style-src-elem
-
Specifies valid sources for stylesheets
<style>
elements and<link>
elements withrel="stylesheet"
. style-src-attr
-
Specifies valid sources for inline styles applied to individual DOM elements.
worker-src
-
Specifies valid sources for
Worker
,SharedWorker
, orServiceWorker
scripts.
Document directives
Navigation directives
Navigation directives govern to which locations a user can navigate or submit a form, for example.
form-action
-
Restricts the URLs which can be used as the target of a form submissions from a given context.
frame-ancestors
-
Specifies valid parents that may embed a page using
<frame>
,<iframe>
,<object>
, or<embed>
. -
Restricts the URLs to which a document can initiate navigation by any means, including
<form>
(ifform-action
is not specified),<a>
,window.location
,window.open
, etc.
Reporting directives
Reporting directives control the reporting process of CSP violations. See also the
Content-Security-Policy-Report-Only
header.
report-uri
Deprecated-
Instructs the user agent to report attempts to violate the Content Security Policy. These violation reports consist of JSON documents sent via an HTTP
POST
request to the specified URI.Warning: Though the
report-to
directive is intended to replace the deprecatedreport-uri
directive,report-to
is not supported in most browsers yet. So for compatibility with current browsers while also adding forward compatibility when browsers getreport-to
support, you can specify bothreport-uri
andreport-to
:http
Content-Security-Policy: …; report-uri https://endpoint.example.com; report-to groupname
In browsers that support
report-to
, thereport-uri
directive will be ignored. report-to
-
Fires a
SecurityPolicyViolationEvent
.
Other directives
require-trusted-types-for
Experimental-
Enforces Trusted Types at the DOM XSS injection sinks.
trusted-types
Experimental-
Used to specify an allowlist of Trusted Types policies. Trusted Types allows applications to lock down DOM XSS injection sinks to only accept non-spoofable, typed values in place of strings.
upgrade-insecure-requests
-
Instructs user agents to treat all of a site's insecure URLs (those served over HTTP) as though they have been replaced with secure URLs (those served over HTTPS). This directive is intended for websites with large numbers of insecure legacy URLs that need to be rewritten.
Deprecated directives
block-all-mixed-content
Deprecated-
Prevents loading any assets using HTTP when the page is loaded using HTTPS.
plugin-types
Deprecated Non-standard-
Restricts the set of plugins that can be embedded into a document by limiting the types of resources which can be loaded.
referrer
Deprecated Non-standard-
Used to specify information in the Referer (sic) header for links away from a page. Use the
Referrer-Policy
header instead.
Values
An overview of the allowed values are listed below. For detailed reference see CSP Source Values and the documentation for individual directives.
Keyword values
'none'
-
Won't allow loading of any resources.
'self'
-
Only allow resources from the current origin.
'strict-dynamic'
-
The trust granted to a script in the page due to an accompanying nonce or hash is extended to the scripts it loads.
'report-sample'
-
Require a sample of the violating code to be included in the violation report.
Unsafe keyword values
'unsafe-inline'
-
Allow use of inline resources.
'unsafe-eval'
-
Allow use of dynamic code evaluation such as
eval
,setImmediate
Non-standard , andwindow.execScript
Non-standard . 'unsafe-hashes'
-
Allows enabling specific inline event handlers.
'unsafe-allow-redirects'
Experimental-
TBD
Hosts values
- Host
- Only allow loading of resources from a specific host, with optional scheme, port, and path. For example,
example.com
,*.example.com
,https://*.example.com:12/path/to/file.js
. - Path parts in the CSP that end in
/
match any path they are a prefix of. For example,example.com/api/
will match URLs likeexample.com/api/users/new
. - Other path parts in the CSP are matched exactly; for example,
example.com/file.js
will matchhttp://example.com/file.js
andhttps://example.com/file.js
, but nothttps://example.com/file.js/file2.js
.
- Only allow loading of resources from a specific host, with optional scheme, port, and path. For example,
- Scheme
- Only allow loading of resources over a specific scheme, should always end with "
:
". For example,https:
,http:
,data:
, etc.
- Only allow loading of resources over a specific scheme, should always end with "
Other values
'nonce-*'
-
A cryptographic nonce (only used once) to allow scripts. The server must generate a unique nonce value each time it transmits a policy. It is critical to provide a nonce that cannot be guessed as bypassing a resource's policy is otherwise trivial. This is used in conjunction with the script tag nonce attribute. For example,
nonce-DhcnhD3khTMePgXwdayK9BsMqXjhguVV
. 'sha*-*'
-
sha256, sha384, or sha512. Followed by a dash and then the sha* value. For example,
sha256-jzgBGA4UWFFmpOBq0JpdsySukE1FrEN5bUpoK8Z29fY=
.
CSP in workers
Workers are in general not governed
by the content security policy of the document (or parent worker) that created them. To
specify a content security policy for the worker, set a
Content-Security-Policy
response header for the request which requested the
worker script itself.
The exception to this is if the worker script's origin is a globally unique identifier (for example, if its URL has a scheme of data or blob). In this case, the worker does inherit the content security policy of the document or worker that created it.
Multiple content security policies
The CSP mechanism allows multiple policies being specified for a resource, including
via the Content-Security-Policy
header, the
Content-Security-Policy-Report-Only
header and a
<meta>
element.
You can use the Content-Security-Policy
header more than once, as in the
example below. Pay special attention to the connect-src
directive here. Even
though the second policy would allow the connection, the first policy contains
connect-src 'none'
. Adding additional policies can only further
restrict the capabilities of the protected resource, which means that there will
be no connection allowed and, as the strictest policy, connect-src 'none'
is enforced.
http
Content-Security-Policy: default-src 'self' http://example.com;
connect-src 'none';
Content-Security-Policy: connect-src http://example.com/;
script-src http://example.com/
Examples
Example: Disable unsafe inline/eval, only allow loading of resources (images, fonts, scripts, etc.) over https:
Using the HTTP header
http
Content-Security-Policy: default-src https:
Using the HTML meta element
html
<meta http-equiv="Content-Security-Policy" content="default-src https:" />
Example: Pre-existing site that uses too much inline code to fix but wants to ensure resources are loaded only over HTTPS and to disable plugins:
http
Content-Security-Policy: default-src https: 'unsafe-eval' 'unsafe-inline'; object-src 'none'
Example: Do not implement the above policy yet; instead just report violations that would have occurred:
http
Content-Security-Policy-Report-Only: default-src https:; report-uri /csp-violation-report-endpoint/
See Mozilla Web Security Guidelines for more examples.
Specifications
Specification |
---|
Content Security Policy Level 3 # csp-header |
Browser compatibility
BCD tables only load in the browser
See also
Content-Security-Policy-Report-Only
- Learn about: Content Security Policy
- Content Security in WebExtensions
- Adopting a strict policy
- CSP Evaluator - Evaluate your Content Security Policy