IIS binding HTTPS Domain name

HTTPS is SSL secure channel, although it is not clear what the specific use, but at least the site looks more than the level of HTTP, access speed also has no impact, so there are conditions, or do, can do gimmicks to bluff people.

WIN2008 system because of port 443 conflict, only one site can be deployed, remember; WIN2012 is not limited.

SSL certificates are free, there are fees, a variety of free, some are not certified by Google, so pick the time is very troublesome.

Fortunately there is a certify software, can automatically apply to let's encrypt request a certificate, and deployment of IIS, including automatic continuation, very convenient, originally HTTPS configuration difficulty factor 10, with this software, at most 1 left.

The operation is as follows:

1, first set the target site in IIS by normal HTTP

2, to certify official website http://certify.webprofusion.com/download and install software to the server, pay attention to its dependence on the NET Framework4.5 environment.

3, open the software, the first time will be prompted to register the mailbox, as prompted to fill;

4, the upper left corner of the new certificate-〉 select the corresponding IIS site, others do not move, click Save;

5, Save finished, click on the right to request a certificate, waiting to return success

6, after the success, the software on the left side will have a display site and expiration time, open the IIS corresponding site, you will find the domain name binding also added corresponding HTTPS header bindings.

At this point, it is recommended to do 301, the other domain names will jump to the HTTPS primary domain name, so that the site will not mess.

Station to the present, did not find anything wrong with the place.

Reference article: https://www.cnblogs.com/duanweishi/p/8483161.html

IIS binding HTTPS Domain name