CSP: manifest-src

Baseline Widely available

This feature is well established and works across many devices and browser versions. It’s been available across browsers since August 2016.

The HTTP Content-Security-Policy: manifest-src directive specifies which manifest can be applied to the resource.

CSP version	3
Directive type	Fetch directive
`default-src` fallback	Yes. If this directive is absent, the user agent will look for the `default-src` directive.

http

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

This directive may have one of the following values:

No resources of this type may be loaded. The single quotes are mandatory.

A space-separated list of source expression values. Resources of this type may be loaded if they match any of the given source expressions.

Source expressions are specified as keyword values or URL patterns: the syntax for each source expression is given in CSP Source Values.

Given this CSP header:

http

Content-Security-Policy: manifest-src https://example.com/

The following <link> is blocked and won't load:

html

<link rel="manifest" href="https://not-example.com/manifest" />

Specification
Content Security Policy Level 3 # directive-manifest-src

BCD tables only load in the browser