https port need to bind SSL Certificates
The method of operation and the following steps:
- Create a certificate in IIS
- View the certificate fingerprint
- Using the command line interface and binding certificate
- The third step can be replaced for the creation of a new empty site, bind to the same port https port and bind the certificate, and then start and stop Web site, and then start owin or dotnetcore procedures, perpetrating a fraud
Using this method the following presentations:
1, create a certificate
Open IIS, on the server node (note, not the site node) Select "Server Certificate", double-click to enter the function, select "Create a self-signed certificate" on the right sidebar
Since matching application function name, OK, the certificate has been created
2. Create a new stations and binds the certificate (assuming that need to use the https port 8048): Fill in name, the Web site points to an empty directory, enable HTTPS, use SSL certificates
3, stop the Web site, or open a Web page real DOTNETCORE owin application, enter the test to test, the certificate will be prompted to risk, because it is self-signed, select "Advanced" to continue
Solution to the risk problem is: use the domain name, and apply a valid certificate for the domain name, and then install the certificate (reference: On the server https://www.cnblogs.com/lxf1117/p/6650647.html ), and on the website use the certificate (step 2)
