X-Frame-Options HTTP response header can be used to indicate whether or not a browser should be allowed to render a page in a
<object> . Sites can use this to avoid clickjacking attacks, by ensuring that their content is not embedded into other sites.
The added security is only provided if the user accessing the document is using a browser supporting
|Header type||Response header|
|Forbidden header name||no|
There are three possible directives for
X-Frame-Options: deny X-Frame-Options: sameorigin X-Frame-Options: allow-from https://example.com/
If you specify
deny, not only will attempts to load the page in a frame fail when loaded from other sites, attempts to do so will fail when loaded from the same site. On the other hand, if you specify
sameorigin, you can still use the page in a frame as long as the site including it in a frame is the same as the one serving the page.
- The page cannot be displayed in a frame, regardless of the site attempting to do so.
- The page can only be displayed in a frame on the same origin as the page itself. The spec leaves it up to browser vendors to decide whether this option applies to the top level, the parent, or the whole chain, although it is argued that the option is not very useful unless all ancestors are also in the same origin (see bug 725490). Also see Browser compatibility for support details.
- The page can only be displayed in a frame on the specified origin. Note that in Firefox this still suffers from the same problem as
sameorigindid — it doesn't check the frame ancestors to see if they are in the same origin.
Note: Setting the meta tag is useless! For instance,
<meta http-equiv="X-Frame-Options" content="deny"> has no effect. Do not use it! Only by setting through the HTTP header like the examples below,
X-Frame-Options will work.
To configure Apache to send the
X-Frame-Options header for all pages, add this to your site's configuration:
Header always set X-Frame-Options "sameorigin"
To configure Apache to set the
X-Frame-Options deny , add this to your site's configuration:
Header set X-Frame-Options "deny"
To configure Apache to set the
allow-from a specific Host , add this to your site's configuration:
Header set X-Frame-Options "allow-from https://example.com/"
To configure nginx to send the
X-Frame-Options header, add this either to your http, server or location configuration:
add_header X-Frame-Options sameorigin;
To configure IIS to send the
X-Frame-Options header, add this to your site's
<system.webServer> ... <httpProtocol> <customHeaders> <add name="X-Frame-Options" value="sameorigin" /> </customHeaders> </httpProtocol> ... </system.webServer>
To configure HAProxy to send the
X-Frame-Options header, add this to your front-end, listen, or backend configuration:
rspadd X-Frame-Options:\ sameorigin
|RFC 7034||HTTP Header Field X-Frame-Options|
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.
|Feature||Android webview||Chrome for Android||Edge mobile||Firefox for Android||Opera Android||iOS Safari||Samsung Internet|
1. Starting in Chrome 61, this applies to all of a frame's ancestors.
2. Starting in Firefox 59, this applies to all of a frame's ancestors.
3. Starting in Opera 48, this applies to all of a frame's ancestors.