This site is the archived OWASP Foundation Wiki and is no longer accepting Account Requests.
To view the new OWASP Foundation website, please visit https://owasp.org
Difference between revisions of "User:Pawel Krawczyk/List of useful HTTP headers"
| Line 55: | Line 55: | ||
'''x-frame-options:''' SAMEORIGIN | '''x-frame-options:''' SAMEORIGIN | ||
'''x-xss-protection:''' 1; mode=block | '''x-xss-protection:''' 1; mode=block | ||
| − | |||
| − | |||
Revision as of 19:03, 14 January 2013
This page lists useful security-related HTTP headers. In most web application frameworks HTTP headers can be set in web server configuration, without changing actual application's code. This is often significantly faster and cheaper solution for at least partial mitigation of existing issues, and a quick additional layer of defense for new applications.
| Field name | Description | Example |
|---|---|---|
| Strict-Transport-Security | Enforces secure-only connections to the server. Complying user agents are to interact with this server using only secure HTTP connections (HTTP over TLS/SSL). | Strict-Transport-Security: max-age=16070400; includeSubDomains
|
| X-Frame-Options, Frame-Options | Clickjacking protection. Values: deny - no rendering within a frame, sameorigin - no rendering if origin mismatch, allow-from: URL - allow rendering frame if loaded from URL | X-Frame-Options: deny
|
| X-XSS-Protection | Cross-site scripting (XSS) filter | X-XSS-Protection: 1; mode=block
|
| X-Content-Type-Options | The only defined value, "nosniff", prevents Internet Explorer and Google Chrom from MIME-sniffing a response away from the declared content-type. This also applies to Google Chrome, when downloading extensions. | X-Content-Type-Options: nosniff
|
| X-Content-Security-Policy, X-WebKit-CSP | Content Security Policy definition. Requires careful tuning and precise definition of the policy. If enabled CSP has significant impact on the way browser renders pages (e.g. inline JavaScript disabled by default and must be explicitly allowed in policy). | X-WebKit-CSP: default-src 'self'
|
Real life examples
Below examples present selected HTTP headers as set by popular websites to demonstrate that they are indeed being used in production services:
As of January 2013 Facebook main page was setting these security related HTTP headers.
Strict-Transport-Security: max-age=60 X-Content-Type-Options: nosniff X-Frame-Options: DENY X-WebKit-CSP: default-src *; script-src https://*.facebook.com http://*.facebook.com https://*.fbcdn.net http://*.fbcdn.net *.facebook.net *.google-analytics.com *.virtualearth.net *.google.com 127.0.0.1:* *.spotilocal.com:* 'unsafe-inline' 'unsafe-eval' https://*.akamaihd.net http://*.akamaihd.net; style-src * 'unsafe-inline'; connect-src https://*.facebook.com http://*.facebook.com https://*.fbcdn.net http://*.fbcdn.net *.facebook.net *.spotilocal.com:* https://*.akamaihd.net ws://*.facebook.com:* http://*.akamaihd.net; X-XSS-Protection: 1; mode=block
Especially interesting is Facebook's use of Content Security Policy (using Google Chrome syntax), whose implementation can be challenging for large sites with heavy usage of JavaScript.
Google+
As of January 2013 Google+ main page was setting these security related HTTP headers:
x-content-type-options: nosniff x-frame-options: SAMEORIGIN x-xss-protection: 1; mode=block
