Ssl – IIS6 Multiple SSL websites to a single HTTP website

You can't use virtual hosts with SSL, so to host two sites both using SSL you have to have 2 ip addresses, each one with a specific host and ssl cert bound to it.

In short you need 2 ip addresses on your server, one bound to domain1.com, and one bound to domain2.com, and 2 IIS sites one for domain1.com, and one for domain2.com. They can both serve up the same content, but will need to be separate sites.

Apache supports something called SNI (see here) which allows you to do vhosts with SSL but this isn't support by IIS currently.

You won't be able to do what you want. You either:

1. Need to obtain a valid certificate for both domains and use the serverHost directives to redirect off SSL (to http://) if you truly don't want to run SSL on that domain.
2. Need to obtain a second IP address and run the domains on seperate IP addresses.
3. Leave SSL Enabled and serve an invalid certificate for domain1

WHY:

1. A client types https://domain1.com/ in a browser
2. The browser resolves this to a TCP connection to on port 443
3. The magic of the internet routes this connection to your server and hopefully into your web server software
4. The client browser is standing at the front door waiting for the proper 'secret handshake' (SSL Cert.)
5. Your server tries the only handshake it knows (which is wrong)
6. The client's browser informs the client that "This guy at the door of domain1.com... He's not who he says he is. This is sketchy"
7. Today, will click the variant of "Proceed Anyway" that their browser presents
8. IF you disable SSL on domain1.com, the user will be shown the other site (quite confusing for the user)
9. IF you leave SSL enabled on domain1.com, modern browsers and webservers will communicate and show the correct site. (albeit, with a scary warning)

If you intend to host domain1.org @ ip on port 80 and domain2.org at ip on port 443 (so that domain2 does not have HTTP access, it should 'work'). Remove the 443 listener for domain1. You will be prompted if any audacious users type https://domain1.org (and then shown domain2). That setup is essentially Port based virtual hosting.Instead of picking random ports you have picked the two defaults and given them to separate virtual hosts. Ultimately in this setup (WITH SSL laying around) the webserver doesn't really care what domain the browser is asking for in the Host header. The web server just cares about the ip:port combo in port based virtual hosts.