Home/ Questions/Q 6795079
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-26T18:17:58+00:00

We have a Win 2008 server running IIS7. The webserver runs several sites, one

  • 0

We have a Win 2008 server running IIS7. The webserver runs several sites, one of which requires SSL for its e-commerce / data-capture components:

I have installed a certificate for domainA and added an HTTPS/443 binding for the http://www.domainA.com website. However, if I try to access https://www.domainB.com, I am shown the content from the domainA site.

How can I prevent all sites using the 443 binding from domainA? When I add the certificate to the binding, I am unable to set the hostname. If I use appcmd to set a hostname, the site gets 2 bindings and access via SSL doesn’t work.

Only domainA should allow access on port 443 and other sites should refuse the connection.

Thanks
James

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    SSL starts connection BEFORE any HTTP header is sent – so clearly the server has now way of distinguishing what domain this connection is for until SSL connection is established.

    Your binding is correct – the other sites are NOT bound to port 443… but by the time the SSL connection is established and the first HTTP header is sent it is already on the IP address (the name has been resolved via DNS).

    As to a solution:

    To circumvent what you see you need to bind domainA.com to a different IP address than the rest (and modify DNS accordingly).

    • 0