CODEWITHSUNDEEP
iisbindingiis-7.5ssl-certificate
user3618129
user3618129

Reputation: 85

IIS 7.5 - can 2 sites run on same port with different FQDN certificate

We used to have a setup on IIS 7.5. - 1 IIS has 2 websites both run on 443. - It has different host names in the binding - site1.domainname.com, site2.domainname.com - Both sites were bound to a wild card SSL cert - *.domainname.com, and this worked fine for years.

Because of an audit, we had to move to a FQDN certificate.

Now when I bind the FQDN certificate on a site, it does not allow me to add a host name.

http://screencast.com/t/sowdaziJV

It says you can't start the second site as another website is already running on the same port.

This made sense until another internal team got it working. My guess is they used scripting to allow this on IIS instead of IIS GUI.

They have 2 websites running on the same port with different SSL certificate with no Hostnames.

I found out an odd thing about their setup and I was able to set it up like that too.

http://screencast.com/t/z5y4n7KhGNE

Questions:

Is IIS running 2 websites on the same port with different FQDN certificate an expected behaviour? I am worried if they took advantage of a bug. I want to be sure if this is allowed before I do this in production.

Upvotes: 0

Views: 1087

Answers (1)

Josh
Josh

Reputation: 10624

They probably turned on SNI. SNI allows the server to discern between a host name and route it to the correct site and then send back the SSL cert associated with the site. The problem is, not all browsers support SNI handshakes. SNI only started with server 2012, so the other team might be running that. Previously, IIS couldn't do this, so each site had to have its own IP / SSL cert. Now, you can run all on 443 for one site, and IIS can figure out which site to respond with by looking at the request.

Upvotes: 1

Related Questions