{{HTTPSidebar}}
The HTTP {{HTTPHeader("Content-Security-Policy")}} form
-action
directive restricts the URLs which can be used as the target of a form submissions from a given context.
CSP version | 2 |
---|---|
Directive type | {{Glossary("Navigation directive")}} |
{{CSP("default-src")}} fallback | No. Not setting this allows anything. |
Syntax
One or more sources can be set for the form-action
policy:
Content-Security-Policy: form-action <source>; Content-Security-Policy: form-action <source> <source>;
<source> can be one of the following:
- <host-source>
- Internet hosts by name or IP address, as well as an optional URL scheme and/or port number. The site's address may include an optional leading wildcard (the asterisk character,
'*'
), and you may use a wildcard (again,'*'
) as the port number, indicating that all legal ports are valid for the source.
Examples:http://*.example.com
: Matches all attempts to load from any subdomain of example.com using thehttp:
URL scheme.mail.example.com:443
: Matches all attempts to access port 443 on mail.example.com.https://store.example.com
: Matches all attempts to access store.example.com usinghttps:
.
- <scheme-source>
- A schema such as 'http:' or 'https:'. The colon is required.
'self'
- Refers to the origin from which the protected document is being served, including the same URL scheme and port number. You must include the single quotes. Some browsers specifically exclude
blob
andfilesystem
from source directives. Sites needing to allow these content types can specify them using the Data attribute. 'unsafe-inline'
- Allows the use of inline resources, such as inline {{HTMLElement("script")}} elements,
javascript:
URLs, inline event handlers, and inline {{HTMLElement("style")}} elements. You must include the single quotes. 'unsafe-eval'
- Allows the use of
eval()
and similar methods for creating code from strings. You must include the single quotes. 'none'
- Refers to the empty set; that is, no URLs match. The single quotes are required.
Examples
Meta tag configuration
<meta http-equiv="Content-Security-Policy" content="form-action 'none'">
Apache configuration
<IfModule mod_headers.c> Header set Content-Security-Policy "form-action 'none'; </IfModule>
Nginx configuration
add_header Content-Security-Policy "form-action 'none';"
Violation case
Using a {{HTMLElement("form")}} element with an action set to inline JavaScript will result in a CSP violation.
<meta http-equiv="Content-Security-Policy" content="form-action 'none'"> <form action="javascript:alert('Foo')" id="form1" method="post"> <input type="text" name="fieldName" value="fieldValue"> <input type="submit" id="submit" value="submit"> </form> // Error: Refused to send form data because it violates the following // Content Security Policy directive: "form-action 'none'".
Specifications
Specification | Status | Comment |
---|---|---|
{{specName("CSP 3.0")}} | {{Spec2('CSP 3.0')}} | No changes. |
{{specName("CSP 1.1")}} | {{Spec2('CSP 1.1')}} | Initial definition. |
Browser compatibility
The compatibility table in this page is generated from structured data. If you'd like to contribute to the data, please check out https://github.com/mdn/browser-compat-data and send us a pull request.
{{Compat}}
See also
- {{HTTPheader("Content-Security-Policy")}}
- {{HTMLElement("form")}}