Content-Security-Policy: manifest-src directive
Baseline
Widely available
This feature is well established and works across many devices and browser versions. It’s been available across browsers since January 2020.
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.
|
Syntax
http
Content-Security-Policy: manifest-src 'none';
Content-Security-Policy: manifest-src <source-expression-list>;
This directive may have one of the following values:
'none'-
No resources of this type may be loaded. The single quotes are mandatory.
<source-expression-list>-
A space-separated list of source expression values. Resources of this type may be loaded if they match any of the given source expressions. For this directive, the following source expression values are applicable:
Examples
Violation cases
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" />
Specifications
| Specification |
|---|
| Content Security Policy Level 3 # directive-manifest-src |
Browser compatibility
| desktop | mobile | |||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
manifest-src
|
|
|
|
|
|
|
|
|
|
|
|
|
Legend
Tip: you can click/tap on a cell for more information.
- Full support
- Full support