You can't use name-based virtual hosting for SSL. More specifically
you cannot have two SSL virtual hosts bound to the
same IP and port. You must either use a different IP or a different
port. Check the FAQ or archives of this list for details of why you
can't do this.
Jamie
On Sunday, February 11, 2001, 9:03:22 PM, you wrote:
> I have 4 virtual servers setup somthing like the following:
> Listen 80
> Listen 443
> NameVirtualHost 1.2.3.4
> <VirtualHost 1.2.3.4:80>
> ServerName www.dom1.com
> </VirtualHost>
> <VitrualHost 1.2.3.4:443>
> ServerName www.dom1.com
> SSLCertificateFile file1.pem
> SSLCertificateKeyFile file1.key
> </VirtualHost>
> <VirtualHost 1.2.3.4:80>
> ServerName www.dom2.com
> </VirtualHost>
> <VirtualHost 1.2.3.4:443>
> ServerName www.dom2.com
> SSLCertificateFile file2.pem
> SSLCertificateKeyFile file2.key
> </VirtualHost>
> When apache starts, it asks me for both passwords to both certs.
> However, if I go to https://www.dom2.com, the certificate for file1.pem
> is presented to the browser. IT IS SUPPOSED to present file2.pem.
> What's wrong?????
______________________________________________________________________
Apache Interface to OpenSSL (mod_ssl) www.modssl.org
User Support Mailing List [EMAIL PROTECTED]
Automated List Manager [EMAIL PROTECTED]
