[andsmith]

I'm trying to setup one of our Windows 2003 Server boxes to host multiple SSL web sites distinguished only by their host header names.

I have setup xyz.com on the server and installed the SSL Cert., the site works great.

I am about to setup 123.com on the server as well. However before I order the cert. I noticed that if I told the website that the SSL port was 443, it would not start. It would get an error because xyz.com was already using port 443.

How do I go about doing this?

I found an article on Technet:

http://www.microsoft.com/technet/prodtechn...941b07554c.mspx

Talking about multiple SSL website's, and using wildcard certs., however I don't this this applies to my situation. I think this is for when you have multiple sites withing the same domain; such as sales.xyz.com and inventory.xyz.com. Is my assumption correct?

Any help would be greatly appreciated.

Thanks,

Andrew

[andsmith]

Nevermind. I've learned you can't have two SSL sites using the same IP.

Andrew

[COERCITAS]

andsmith, on Sep 16 2005, 09:14 PM, said:

Nevermind.  I've learned you can't have two SSL sites using the same IP.

Andrew
<{POST_SNAPBACK}>

Absolutely (hello btw ), but you still can assign several IP addresses to the same interface

PS : the reason is that regular HTTP header is containing site's name if needed, so you can have more than one HTTP ONLY site on the same IP address (thus, only the site's name will separate them) BUT HTTPS is "only" dealing with IP address, thus you can't have 2 different HTTPS sites on the same IP address (non sense). This is easily bypassed just by adding another IP address to the interface and then, assign said site to its own IP address (you can't stay with the default ANY setting in that case).

This post has been edited by COERCITAS: 20 September 2005 - 06:37 AM