CSP: object-src
The HTTP Content-Security-Policy
object-src directive specifies valid sources for the
<object> and <embed> elements.
Note:
Elements controlled by object-src are perhaps coincidentally
considered legacy HTML elements and aren't receiving new standardized features (such as
the security attributes sandbox or allow for
<iframe>). Therefore it is recommended to restrict
this fetch-directive (e.g. explicitly set object-src 'none' if possible).
| CSP version | 1 |
|---|---|
| Directive type | Fetch directive |
default-src fallback |
Yes. If this directive is absent, the user agent will look for the
default-src directive.
|
Syntax
Content-Security-Policy: object-src 'none';
Content-Security-Policy: object-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:
Content-Security-Policy: object-src https://example.com/
The following <object> and <embed> elements are blocked and won't load:
<embed src="https://not-example.com/flash"></embed>
<object data="https://not-example.com/plugin"></object>