Well, you mix two different things. You enter blank wildcard certificates and SNI (server name). They are certainly different solutions to such problems.
Wildcard certificates do not use header verification to encrypt your traffic, you simply specify the DNS at the desired IP address, and your request is sent to any site that you configured in IIS.
SNI is different and is what you want. SNI checks each HTTP request and determines which IIS site you want to use based on host headers. Before SNI existed, you could not verify headers in SSL requests because headers were also encrypted.
When using SNI, if you have certificates for each site (wildcard certificates or individual site certificates, UCC certificates, or some combination of them), you can use SNI to verify each HTTP request and maintain the corresponding SSL certificate and site. You can do this for as many websites as you want, and share 1 IP: port combination at all.
Here is a WikiPedia article that explains this in a bit more detail:
http://en.wikipedia.org/wiki/Server_Name_Indication#Background_of_the_problem
Here is an article on how to configure it in IIS 8 and higher :
https://www.digicert.com/ssl-certificate-installation-microsoft-iis-8.htm#multiple
At step 18, these instructions indicate where you enable SNI.
Here is an article on how to configure it in Apache 2.2.12 and higher :
https://www.digicert.com/ssl-support/apache-multiple-ssl-certificates-using-sni.htm
source share