Deploying HTTPS "reprint" in the IIS environment

1, first we have to take away our certificate, stored in our local computer, and then copied to the server.

2. What do you do next after you take it away? Open the file, of course, and see what's inside. We found the IIS compressed package and unzipped it.

3, parse to get PFX file, that is, we need to deploy a domain name certificate file.

4, small partners can do these parsing on the server, but also can be like a small part of the local, and then create a folder within the server, the need to copy the things in it. (Do not cut, you know, even if you do not know you will go to Baidu)

5. Then open the IIS Control Panel for the server.

6. Then open the IIS home page to find the server certificate bar, double-click to open.

7, double-click Open, select Import, import the PFX file we just extracted, this PFX file is the one you need to deploy the domain name of the file.

8, this time we take HTTPS to open our deployment of the website, now show is still red.

9, now we go to find the site we need to deploy, in the Server site column, double-click bindings.

10. Then we click Add, add, add select https,443 port.

11, this time we open the HTTPS website through the browser.

12, Green has there? Green, green, ah ... It's green. Fell in love with a wild horse, but my home has no prairie, but it is green a piece ... Security small lock sign AH no ... Wait, did we forget something? When we open the www.domain.com again, it's still gray. There is still no green, this kind of want to be green feel? (Suddenly good distressed baby).

13, you Baby Mo Panic, hold me tight, next small taping everyone how to access the default is the HTTPS path. To do the default access to HTTPS, you may want to do jump, but HTTPS seems to have a tall name called URL rewrite. We need to download a rewrite component on IIS.

IIS7.5:

English 32-bit: Http://download.microsoft.com/download/4/9/C/49CD28DB-4AA6-4A51-9437-AA001221F606/rewrite_x86_zh-CN.msi

English 64-bit: Http://download.microsoft.com/download/4/E/7/4E7ECE9A-DF55-4F90-A354-B497072BDE0A/rewrite_x64_zh-CN.msi

English: Http://www.iis.net/downloads/microsoft/url-rewrite

IIS 8 Installation URL rewrite reference http://shiyousan.com/post/635646254870261696

After the download, you will find that our IIS interface has a URL rewrite of the components, no beginning, yes, I was just down.

The only way to make use of URL rewriting is to implement HTTP jump HTTPS.

So, before you deploy, Please check the Web site root directory if there is a Web. config file, if so, please back up the Web. config file here, because the following configuration May and Web. config jump conflict, personal suggestions are directly deleted processing, after all, the old do not go to the new not to come, hahaha (recommended first backup).

14. Then continue to the next step, double-click Open, add Rule.

15. Fill in the rule name: Redirect to HTTPS, use regular expressions, fill in the pattern (. *), and then select Add Condition. The first {HTTPS} matches the pattern ^off$, and the second fill {https_host} does not match the pattern ^ (localhost).

16. Type of action Select Redirect, and then select Properties for https://{http_host}/{r:1} redirection type Select 303.

17, the last step, check the next point to save.

18, now we can go to see our website, direct input www.domain.com.

The above is the tutorial is implemented in the IIS7 environment, very simple, very soon.

Multiple HTTPS bound under one IIS

1. Find C:\Windows\system32\inetsrv\config\applicationHost.config

2. <binding protocol= "https" bindinginformation= "*:443"/>

Modified to:

<binding protocol= "https" bindinginformation= "*:443:www.baidu.om"/>

MIME type

Extension:.

Type: Application/octet-stream

Deploying HTTPS "reprint" in the IIS environment