CONFIGURE A HOST HEADER FOR A WEB SITE IN IIS7 WINDOWS 2008 WHERE SNI IS NOT SUPPORTED
If you want to host more than one Web site on a Web server, you can assign each Web site a unique IP address, specify a non-standard TCP port number for a Web site, or utilise host headers to distinguish each Web site from the others. The use of host headers is more widespread than the assignment of unique IP addresses to Web sites or the use of non-standard TCP port numbers, which are the other two approaches.
Multiple websites hosted on the same server can be bound to port 443, however doing so via the GUI is difficult due to the Host name being greyed out, as illustrated in Figure 1. If the SSL Certificate, on the other hand, begins with a *, it indicates that it is enabled. As illustrated in Figure 2, this is expected to enable wildcard certificates.
Figure 1: The hostname has been greyed out.
When you try to connect multiple SSL certificates to distinct websites, and both of them want to use port 443, you will run into difficulties. That is not going to work.
The friendly name of the certificate installed can be changed with a simple edit by adding * before the friendly name, as seen in figure 2. That * does not necessarily imply that the certificate is a wildcard certificate.
This will enable the Host name Section, where you will be able to enter the exact URLs and bind numerous SSL certificates to a single IP and port combination, allowing you to do more with less.
Using the CLI
1)After opening the command prompt with administrative permissions, navigate to the directory C:InetpubAdminScripts.
2) Enter the command listed below.
“:443:host header>” is the SecureBindings for the /w3svc/site identifier>/SecureBindings parameter set by cscript.exe and adsutil.vbs.
The host header value for a Web site is represented by the tag host header> (www.myothersite.com). This is the IIS site ID that appears when you are browsing through all of the websites in Internet Information Services (IIS).
Carry out this command for each of the websites that will be using the certificate in question. They will then utilise the same certificate that was previously installed on the IP address for the first site.