Warning

The CSP has directives browsers ignore

The short version

Fix the listed directives.

What it means

Your Content-Security-Policy contains directive names browsers don't recognise, usually a typo such as scripts-src, or a directive that only works elsewhere. The detail lists the ignored names.

Why it matters

Browsers skip unknown directives silently, so a typo can leave a whole category unprotected while the policy looks complete. A misspelled script-src means scripts fall back to default-src, or to no restriction at all. Our check lists the names it skipped, so you can compare them with the policy you meant to send, line by line.

How to fix it

  1. Compare each listed directive with the CSP Level 3 names: default-src, script-src, style-src, img-src, connect-src, font-src, frame-src, frame-ancestors, object-src, base-uri, form-action and the others in the specification.
  2. Fix the spelling, or remove directives that are deprecated, such as plugin-types or block-all-mixed-content (use upgrade-insecure-requests instead).
  3. Separate directives with semicolons and sources with spaces.

Check it worked

Run the HTTP and security headers check again. The finding should be gone once every directive is one browsers recognise.