I have a Windows 2000 server running IIS 5.
There are 2 sites in my server...

1. www.AAA.com (SSL installed)
2. www.BBB.com (no SSL)

Recently I got a quick SSL for www.AAA.com and installed, works fine. But when I type https://www.BBB.com it shows the site https://www.AAA.com instead! :confused:

Does anyone know why did this happen?
Will there be a conflict if I get another SSL for www.BBB.com?

Thanks a million...

windows does not support multiple ssl sites on a single ip address
so if the ip of www.AAA.com and www.BBB.com are the same then it will show AAA.com and if you try to add ssl for BBB.com it will fail. so for secure sites each customer needs an ip on windows.

Is this the same for Apache 1.3.31 on RH? I think it is, but just wanted to confirm.

Yes, this applies to all Web server.
1 SSL -> 1 Dedicated IP

I hate to rehash an old topic but thats not exactly true....

You can have a plethora of SSL certificates per a single IP and it isn't difficult with Apache 2

You can make:

http://www.site1.com
http://www.site2.com

Both have the same ip, and yet have two distinct SSL layers, despite what common knowledge preaches. Apache docs are your friend.

Apache Docs tell you explicitly "No."

The docs don't tell you "yes"...they tell you how to use modules that you can use to make this work.

Sometimes you have to use your imagination I guess.

There's no way you can do it on the standard HTTPS port. The SSL handshake is established before the HTTP request is sent, and since the SSL certificate has the domain name embedded in it, any redirection tricks will get bounced back by the browser as a certificate mismatch.

Now, you can run multiple SSL certs on one IP on separate ports, which might just work depending on your intended application.