HTTP Strict Transport Security

Revision as of 20:17, 6 August 2011 by Daniel Black (talk | contribs) (the spec is a IETF activity more than a W3C activity so change the reference URL)

Jump to: navigation, search
This article is a stub. You can help OWASP by expanding it or discussing it on its Talk page.


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.


Example of the HTTP strict transport security header

 Strict-Transport-Security: max-age=60000

If all subdomains are HTTPS to then the following header is applicable:

 Strict-Transport-Security: max-age=60000; includeSubDomains

Browser Support

Lowest Version Supported
Internet Explorer
no support

Server Side

The web server side needs to inject the HSTS header.

For HTTP sites on the same domain it is not recommended to add a HSTS header but to do a perminate redirect (301 status code) to the HTTPS site.

An Apache HTTPd example that will permanently redirect a URL to the identical URL with a HTTPS scheme, is as follows:

<VirtualHost *:80>
       ServerAlias *
       RewriteEngine On
       RewriteRule ^(.*)$ https://%{HTTP_HOST}$1 [redirect=301]

On the HTTPS site configuration the following is needed to add the header as recommended by the standard:

       Header set Strict-Transport-Security "max-age=16070400; includeSubDomains"

The following links show how to do set response headers in other web servers:


HSTS Spec entry

MDN Docs for HSTS

OWASP TLS Protection Cheat Sheet

Firefox STS Support

Google Chrome STS Support