> Does this mean that http://www.testing.com and https://www.testing.com
cannot have the same IP address?
>
Er, well, they have to have the same IP address, since DNS is not
protocol-specific.
What he means is that if you wanted https://www.testing.com and
https://abc.testing.com/ to be virtual hosts, then they would have to be
IP-based virtual hosts, not name-based virtual hosts -- i.e. they would need
different IPs. This is because the SSL server has to send out a certificate
before the browser has a chance to tell it which hostname it is using --
thus, you can't do name-based virtual hosting with SSL, since the server
can't tell which virtual host to use. See the mod_ssl FAQ for more info.
However, you can make http://www.testing.com and https://www.testing.com
different virtual hosts, by specifying the different ports:
<VirtualHost www.testing.com:80>
DocumentRoot /www/insecure/htdocs
</VirtualHost>
<VirtualHost www.testing.com:443>
DocumentRoot /www/secure/htdocs
</VirtualHost>
Cheers,
Simon Garner
______________________________________________________________________
Apache Interface to OpenSSL (mod_ssl) www.modssl.org
User Support Mailing List [EMAIL PROTECTED]
Automated List Manager [EMAIL PROTECTED]
