Content-Security-Policy: fenced-frame-src directive
Deprecated
To be removed
This feature is pending removal from browsers. Using it now may lead to broken functionality in future updates.
Following the announcement that Chrome will maintain its current approach to third-party cookies, Chrome decided to withdraw certain Privacy Sandbox features including the <fencedframe> element and related APIs.
Experimental: This is an experimental technology
Check the Browser compatibility table carefully before using this in production.
The HTTP Content-Security-Policy (CSP)
fenced-frame-src directive specifies valid sources for nested browsing contexts loaded into <fencedframe> elements.
| CSP version | 1 |
|---|---|
| Directive type | Fetch directive |
| Fallback |
If this directive is absent, the user agent will look for the
frame-src directive (which falls back to the
child-src directive).
|
Syntax
Content-Security-Policy: fenced-frame-src <source-expression-list>;
<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:
- The
<host-source>value"https:" - The
<scheme-source>value"https:" - The string
"*"
- The
Examples
Violation cases
Given this CSP header:
Content-Security-Policy: fenced-frame-src https://example.com/
The following sources will not load in a fenced frame:
https://not-example.com/(domain doesn't match)https://example.org/(TLD doesn't match)
Specifications
| Specification |
|---|
| Fenced Frame # new-csp-directive |