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 "HTTP Strict Transport Security"
(dropping server config data, way to basic info) |
(moving threats) |
||
Line 51: | Line 51: | ||
<br> | <br> | ||
A detailed overview of supporting browsers can be found at [http://caniuse.com/#feat=stricttransportsecurity caniuse.com]. | A detailed overview of supporting browsers can be found at [http://caniuse.com/#feat=stricttransportsecurity caniuse.com]. | ||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
== Links == | == Links == |
Revision as of 19:40, 8 July 2015
Description
HTTP Strict Transport Security (HSTS) is an opt-in security enhancement that is specified by a web application through the use of a special response header. Once a supported browser receives this header that browser will prevent any communications from being sent over HTTP to the specified domain and will instead send all communications over HTTPS. It also prevents HTTPS click through prompts on browsers.
The specification has been released and published end of 2012 as RFC 6797 (HTTP Strict Transport Security (HSTS)) by the IETF. (Reference see in the links at the bottom.)
Examples
Simple example, using a long (1 year) max-age:
Strict-Transport-Security: max-age=31536000
If all present and future subdomains will be HTTPS:
Strict-Transport-Security: max-age=31536000; includeSubDomains
Recommended: If the site owner would like their domain to be included in the HSTS preload list maintained by Chrome (and used by Firefox and Safari), then use:
Strict-Transport-Security: max-age=31536000; includeSubDomains; preload
The `preload` flag indicates the site owner's consent to have their domain preloaded. The site owner still needs to then go and submit the domain to the list.
Always Use includeSubDomains
The lack of use of includeSubDomains can lead to a significant privacy leak[1]. Be sure to use includeSubDomains on all wildcard certificates, at least.
Browser Support
Browser |
Support Introduced |
Internet Explorer |
Internet Explorer 11 on Windows 8.1 and Windows 7[2] |
Firefox |
4 |
Opera |
12 |
Safari |
Mavericks (Mac OS X 10.9) |
Chrome |
4.0.211.0 |
A detailed overview of supporting browsers can be found at caniuse.com.