Application Initialization module fails when web site requires SSL

Applies to: ASP.NET


Application Initialization module formerly known as “Application Warmup” is not working for web site configured to require SSL.


This behavior is by design.

The warm-up module sends the request using HTTP protocol and not with HTTPS. The workaround suggested will allow HTTP requests to localhost from warm up module but it redirects to the HTTPS for the rest of the requests so by design here means that the warm up module makes requests over HTTP.


To workaround this limitation, you may consider enabling HTTP (uncheck the "Require SSL" setting in IIS Manager/SSL Settings) and use a URL Rewrite rule to redirect HTTP requests to HTTPS with the exception of the request coming from the warmup module : 

<rule name="No redirect on warmup request (request from localhost with warmup user agent)" stopProcessing="true">>
<match url=".*" />
<add input="{HTTP_HOST}" pattern="localhost" />
<add input="{HTTP_USER_AGENT}" pattern="Initialization" />
<action type="Rewrite" url="{URL}" />
<rule name="HTTP to HTTPS redirect for all requests" stopProcessing="true">
<match url="(.*)" />
<add input="{HTTPS}" pattern="off" />
<action type="Redirect" url="https://{HTTP_HOST}/{R:1}" />