Today the Spinach garden for everyone to share the article is how to make a VPS to achieve multiple website HTTPS access. We know that in the early days of SSL certificate design, the default is that a server can only provide a single service. Or, an IP can only provide one service. But later with the development of virtual machines, a server often hosted a lot of sites, which led to a VPS can only make a website to achieve HTTPS access this embarrassment.
Fortunately, SNI (server Name indication) is defined in RFC 4366, which improves the transfer of SSL/TLS, allowing the server to return the corresponding certificate based on the corresponding domain name when the client initiates an HTTPS handshake request. So with today's spinach garden to share the article.
Warm tip: The following operations are Spinach Garden in the Windows Server +IIS8 environment operation. Other environments, please test yourself.
1. Open the registry: Win+r key to run, enter "regedit".
2. Locate the registry key: Hkey_local_machine\system\currentcontrolset\services\http\parameters\sslsnibindinginfo, change the registry value to 2.
3. Restart the IIS service.
4, install the SSL certificate. This online many methods, you can also refer to the "HTTPS to your website plus lock."
5. Bind the SSL certificate to a different Web site. Please look
Locate the website where you want to bind the certificate, click "SSL Settings" and click "bind". The following window pops up.
Click "Edit", select "https", enter the IP address, bind the domain name, hook the following tick, select the corresponding certificate, click OK. This step is critical, mainly to bind the SSL certificate to the domain name. When a user accesses a domain name, the corresponding certificate is returned, so a server can implement different websites to bind different certificates, so that multiple websites can be accessed through HTTPS at the same time.
Reproduced from Spinach Garden
How to make an IIS server implement multiple Web site HTTPS access