Sysadmins of the North

Technical blog, where topics include: computer, server, web, sysadmin, MySQL, database, virtualization, optimization and security

How to enable HTTP Strict-Transport-Security (HSTS) on IIS

Set up HTTP Strict-Transport-Security (HSTS) in Windows Server IIS. Scott Hanselman wrote a great post on how to enable HTTP Strict-Transport-Security (HSTS) on IIS web servers, and here is some more technical information about HSTS in IIS (and other security headers)

Enable and serve an HTTP Strict Transport Security (HSTS) response header in IIS

HTTP Strict Transport Security (HSTS) is a web security policy mechanism which is necessary to protect secure HTTPS websites against downgrade attacks, and which greatly simplifies protection against cookie hijacking.

​HSTS improves security and prevents man-in-the-middle attacks, downgrade attacks, and cookie-hijacking.

It allows web servers to declare that web browsers (or other complying user agents) should only interact with it using secure HTTPS connections, and never via the insecure HTTP protocol. HSTS is an IETF standards track protocol and is specified in RFC 6797.

The HSTS Policy is communicated by the server to the user agent via an HTTP response header field named Strict-Transport-Security. HSTS Policy specifies a period of time during which the user agent should only access the server in a secure fashion.

Therefore, adding a HSTS header is important after you’ve added SSL to your WordPress website, so browsers automatically request your HTTPS address.

Read the blog post: How to enable HTTP Strict Transport Security (HSTS) in IIS7+. Basically, all you need to add to your web.config for HSTS configuration, is an Outbound Rule, to rewrite request responses and sending the HTTP Strict Transport Security response header:

	<rule name="Add Strict-Transport-Security when HTTPS" enabled="true">
		<match serverVariable="RESPONSE_Strict_Transport_Security" pattern=".*" />
			<add input="{HTTPS}" pattern="on" ignoreCase="true" />
		<action type="Rewrite" value="max-age=31536000" />

Protip: While your at it, don’t forget to remove the IIS Server: response header, and ETag as well.

HSTS and includeSubdomains

Do you have your SSL (TLS) certificate on your www. subdomain? Then you need to include it using includeSubdomains. The outboundRules rule then becomes:

<rule name="Add Strict-Transport-Security when HTTPS" enabled="true">
	<match serverVariable="RESPONSE_Strict_Transport_Security" pattern=".*" />
		<add input="{HTTPS}" pattern="on" ignoreCase="true" />
	<action type="Rewrite" value="max-age=31536000; includeSubDomains; preload" />

If you include the preload flag, your site is eligible to be included in Chrome’s HSTS preload list (also used by Firefox and Safari). You’ll find more information about this in OWASP’s HSTS HTTP Strict Transport Security examples.

HSTS header in WordPress functions.php

You can set a HSTS header in WordPress through your functions.php theme file as well. For this to happen, you can hook into the send_headers action.

Use the following code in your functions.php to send a HSTS header from WordPress:

add_action( 'send_headers', 'saotn_add_hsts_header' );
function saotn_add_hsts_header() {
	header( 'Strict-Transport-Security: max-age=31536000; includeSubDomains; preload' );

Want to know more about SSL in WordPress? See my article SSL in WordPress: how to move WordPress to HTTPS? The definitive guide.


High-risk vulnerabilities in TheCartPress leaves WordPress sites at risk


My WordPress web.config


  1. Chris

    I’m curious about your first solution using outboundRules. What are the pros and cons to this vs your other page where you detail other options? Everything I’ve tried is producing a redirect loop except for this outboundRules way.

    Also, if you could speak more to the options shown like “max-age” then that would be great.


    • Jan Reilink

      Hi Chris, thank you for your comment!

      HSTS allows you to configure your visitor’s browser to only communicate with you via HTTPS. And the max-age directive tells the browser how long to cache this

      Scott Helme has all relevant information about max-age, and other HSTS directives in his HSTS Cheat Sheet. You might also like OWASP’s HSTS Cheat Sheet:

      About the Outbound Rule: unfortunately you cannot set all types of responses using web.config’s customHeaders section. In this particular case, you need to rewrite the output stream to add HSTS to the headers that are sent out.

      And here lies the con; you rewrite already dynamically generated HTTP output. There may be a (small) performance penalty.

      Fortunately this has changed in IIS 10.0, in Windows Server 2016. I still need to rewrite this article, but see on how to use customHeaders web.config node to set the HSTS header in HTTPS responses – only in Windows Server 2016 (IIS 10.0) Version 1709, Fall Creators Update.

  2. Anonymous

    i love u man.. thanks!!

Hi! Join the discussion, leave a reply!

This site uses Akismet to reduce spam. Learn how your comment data is processed.

Powered by WordPress & Theme by Anders Norén

%d bloggers like this: