HTTP - Content security policy (CSP)


CSP 1) is a security response header that define the behaviors that are trusted in your HTML page.

CSP can be used to detect and mitigate against the effects of certain attacks, such as:

CSP is particularly powerful as it includes directives such as script-src that specifies what are valid, allowed sources for JavaScript.


Google Publisher tag

Ref: If you have a Content Security Policy (CSP) on your site, the restrictions of the CSP also apply to AMPHTML ads in friendly iframes. In that case, call googletag.pubads().setForceSafeFrame(true) before making any ad requests, to allow the ad to render in a cross-domain iframe without the CSP's restrictions


Content-Security-Policy: <policy-directive>; <policy-directive>
  • With a few exceptions, policies mostly involve specifying server origins and script endpoints.
  • Your policy should include a default-src policy directive, which is a fallback for other resource types when they don't have policies of their own



Third party script

Content-Security-Policy: script-src
<script src=""></script>

Block HTTP call on HTTPS page

<meta http-equiv="Content-Security-Policy" content="block-all-mixed-content" />


Content-Security-Policy-Report-Only: default-src 'self' *; img-src ; report-uri 

Example of Json send. The definition can be found in the specification.

  "csp-report": {
    "document-uri": "",
    "referrer": "",
    "blocked-uri": "",
    "violated-directive": "style-src",
    "original-policy": "default-src 'none'; style-src; report-uri /_/csp-reports",
    "disposition": "report"

Powered by ComboStrap