{"id":2522,"date":"2013-10-16T20:54:03","date_gmt":"2013-10-16T12:54:03","guid":{"rendered":"http:\/\/rmohan.com\/?p=2522"},"modified":"2013-10-16T21:01:30","modified_gmt":"2013-10-16T13:01:30","slug":"iis7-redirect-http-to-https","status":"publish","type":"post","link":"https:\/\/mohan.sg\/?p=2522","title":{"rendered":"IIS7 redirect HTTP to HTTPS"},"content":{"rendered":"
\n

Memorise<\/a><\/h1>\n<\/header>\n

IIS7 redirect HTTP to HTTPS<\/h2>\n

The method of setting up an IIS7 redirect HTTP to HTTPS is to Require SSL on the site or part of the site and set up a custom 403.4 error page. To do this, just following these steps:<\/p>\n

    \n
  1. Install your SSL certificate in IIS 7<\/a>\u00a0and bind it to your website<\/li>\n
  2. In IIS, click on the site name, and go to the\u00a0SSL Settings\u00a0<\/strong>section<\/li>\n
  3. Check\u00a0Require SSL<\/strong>\u00a0and\u00a0Require 128-bit SSL<\/strong>\u00a0and click\u00a0Apply<\/strong><\/li>\n
  4. After doing this, users will normally receive error:<\/li>\n
  5. Create a new text file and paste the following into it:<\/li>\n<\/ol>\n

    <html>
    \n<head><title>Redirecting\u2026<\/title><\/head>
    \n<script language=\u201dJavaScript\u201d>
    \nfunction redirectHttpToHttps()
    \n{
    \nvar httpURL= window.location.hostname + window.location.pathname + window.location.search;
    \nvar httpsURL= \u201chttps:\/\/\u201d + httpURL;
    \nwindow.location = httpsURL;
    \n}
    \nredirectHttpToHttps();
    \n<\/script>
    \n<body>
    \n<\/body>
    \n<\/html><\/p>\n

    6. Save the file as\u00a0redirectToHttps.htm<\/strong>\u00a0in your C:\\Inetpub directory<\/p>\n

    7. Back in IIS, click on the site name and double-click the\u00a0Error Pages<\/strong>\u00a0option<\/p>\n

    8. Click\u00a0Add\u2026<\/strong>\u00a0and enter\u00a0403.4<\/strong>\u00a0as the Status code. Browse for the redirectToHttps.htm file you just created and click\u00a0OK<\/strong><\/p>\n

    9. Select the error code and press\u00a0Edit Feature Settings\u2026<\/strong><\/p>\n

    10. Click the\u00a0Custom error pages<\/strong>\u00a0option and again browse for the redirectToHttps.htm file<\/p>\n

    11. Test the site by going to http:\/\/www.yoursite.com and making sure it redirects<\/p>\n

    A caveat of using a custom error page to do an IIS7 redirect from HTTP to HTTPS is that the web browser must have JavaScript enabled for the redirection to work.<\/p>\n

    If you get \u201cLock violation\u201d error in IIS 7.5<\/p>\n

    All you need to do is to open file \u201c%windir%\\System32\\inetsrv\\config\\applicationHost.config\u201d and remove \u2018defaultPath\u2019 from the following line:<\/p>\n

    <httpErrors lockAttributes=\u201dallowAbsolutePathsWhenDelegated,defaultPath\u201d><\/p>\n

     <\/p>\n

    GUI Version<\/h2>\n

     <\/p>\n

    URL Rewrite has a GUI to allow you to enter rules within IIS 7; in the background all this does is edit the web.config file of the site. I will show you how to create a rule both ways.<\/p>\n

    In the following example we will redirect HTTP to HTTPs using URL Rewrite. You will need the following items completed in order for this to work correctly.<\/p>\n

    – SSL Certificate for site installed in IIS.
    \n– Site properly installed and configured for SSL (site set up and binding in IIS configured).
    \n– URL Rewrite 2.0 is installed on the sever.<\/p>\n

    GUI Version<\/h2>\n

    – Select the website you wish to configure
    \n– In the \u201cFeatures View\u201d panel, double click URL Rewrite<\/p>\n

    \"031010_2252_Automatical1\"<\/a><\/p>\n

    You will notice there are currently no rules configured for this site. Click \u201cAdd Rules\u2026\u201d in the Actions menu to the right of the \u201cFeatures View\u201d panel\"031010_2252_Automatical2\"<\/a><\/p>\n

     <\/p>\n

     <\/p>\n

    Use the default \u201cBlank rule\u201d and press \u201cOK\u201d.<\/p>\n

    \"031010_2252_Automatical3\"<\/a><\/p>\n

    When editing a rule there are the \u201cName\u201d field and 4 configuration pull down boxes.<\/p>\n

     <\/p>\n

    – Enter \u201cRedirect to HTTPS\u201d in the name field.
    \n– Next we will configure the first configuration pull down box called \u201cMatch URL\u201d, on the right side of \u201cMatch URL\u201d press the down arrow to expand the box.<\/p>\n

     <\/p>\n

     <\/p>\n

    Within the \u201cMatch URL\u201d configuration box we will set the following settings:<\/p>\n

     <\/p>\n

    Requested URL:<\/strong> Matches the Pattern
    \nUsing:<\/strong> Regular Expressions
    \nPattern:<\/strong> (.*)<\/p>\n

     <\/p>\n

     <\/p>\n

    \"031010_2252_Automatical4\"<\/a><\/p>\n

    We can now edit the next configuration pull down box which is \u201cConditions\u201d, Press \u201cAdd\u2026\u201d to add a new condition to the configuration<\/a><\/p>\n

    \"031010_2252_Automatical5\"<\/a><\/p>\n

     <\/p>\n

    We will configure the condition with the following settings:<\/p>\n

    Condition Input<\/strong>: {HTTPS}
    \nCheck if input string<\/strong>: Matches the Pattern
    \nPattern<\/strong>: ^OFF$<\/p>\n

    Press \u201cOK\u201d<\/p>\n

    href=”http:\/\/rmohan.com\/wp-content\/uploads\/2013\/10\/031010_2252_Automatical7.png”>\"031010_2252_Automatical7\" \"031010_2252_Automatical8\"<\/a> \"031010_2252_Automatical9\"<\/a> \"031010_2252_Automatical10\"<\/a><\/p>\n

    You should now see the rule configured on the main screen of the URL Rewrite module.<\/p>\n

    Test your site, it should now redirect from HTTP to HTTPS.<\/p>\n

    If we exam the web.config file we can see where the rule was entered. If we entered the rule directly into the web.config file it would show up in the GUI.<\/p>\n

    \"031010_2252_Automatical11\"<\/a>
    \nTest your site, it should now redirect from HTTP to HTTPS.<\/p>\n

    If we exam the web.config file we can see where the rule was entered. If we entered the rule directly into the web.config file it would show up in the GUI.<\/p>\n

    \"031010_2252_Automatical12\"<\/a><\/p>\n

    Web.Config Rule<\/p>\n

    You can also edit the web.config file of the site directly and you will be able to see the rule in the GUI. You will need to enter the following within the <system.webServer> <\/system.webServer> elements.<\/p>\n

     <\/p>\n

    \n
    <<\/code>rule<\/code> name<\/code>=<\/code>\"Redirect to HTTPS\"<\/code> stopProcessing<\/code>=<\/code>\"true\"<\/code>><\/code><\/div>\n
    <<\/code>match<\/code> url<\/code>=<\/code>\"(.*)\"<\/code> \/><\/code><\/div>\n
    <<\/code>conditions<\/code>><<\/code>add<\/code> input<\/code>=<\/code>\"{HTTPS}\"<\/code> pattern<\/code>=<\/code>\"^OFF$\"<\/code> \/><\/code><\/div>\n
    <\/<\/code>conditions<\/code>><\/code><\/div>\n
    <<\/code>action<\/code> type<\/code>=<\/code>\"Redirect\"<\/code> url<\/code>=<\/code>\"https:\/\/<\/a>{HTTP_HOST}\/{R:1}\"<\/code> redirectType<\/code>=<\/code>\"SeeOther\"<\/code> \/><\/code><\/div>\n
    <\/<\/code>rule<\/code>><\/code><\/div>\n
    When implementing this solution you need to make sure to use relative paths for all references on your page because there is a possibility you will get a warning asking you if you want to display secure and insecure items. For example, if you have a logo on your page and the URL to this logo is http:\/\/domain\/images\/logo.jpg, do not use the whole path because including the http:\/\/ will hard code this image to use http and not https<\/div>\n<\/div>\n","protected":false},"excerpt":{"rendered":"

    Memorise IIS7 redirect HTTP to HTTPS <\/p>\n

    April 14, 2013<\/p>\n

    The method of setting up an IIS7 redirect HTTP to HTTPS is to Require SSL on the site or part of the site and set up a custom 403.4 error page. To do this, just following these steps:<\/p>\n

    Install your SSL certificate in IIS 7 […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[35],"tags":[],"_links":{"self":[{"href":"https:\/\/mohan.sg\/index.php?rest_route=\/wp\/v2\/posts\/2522"}],"collection":[{"href":"https:\/\/mohan.sg\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/mohan.sg\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/mohan.sg\/index.php?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/mohan.sg\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=2522"}],"version-history":[{"count":1,"href":"https:\/\/mohan.sg\/index.php?rest_route=\/wp\/v2\/posts\/2522\/revisions"}],"predecessor-version":[{"id":2535,"href":"https:\/\/mohan.sg\/index.php?rest_route=\/wp\/v2\/posts\/2522\/revisions\/2535"}],"wp:attachment":[{"href":"https:\/\/mohan.sg\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=2522"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/mohan.sg\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=2522"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/mohan.sg\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=2522"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}