> Aha. That makes sense to me. I noticed this discussion
> because I was
> considering doing this sort of thing in the next month or
> two. Damn! Now I
> have to provide IP addresses for virtual sites that require
> this support. :(
Might not something like this work? It gives you name based virtual hosts
for the http part...
NameVirtualHost 12.34.56.78:80
<VirtualHost 12.34.56.78:80>
ServerName domain1.com
Redirect / https://domain1.com:1443
</VirtualHost>
<VirtualHost 12.34.56.78:80>
ServerName domain2.com
Redirect / https://domain2.com:1444
</VirtualHost>
<VirtualHost 12.34.56.78:1443>
ServerName domain1.com
CustomLog "..."
ErrorLog "..."
SSLEngine on
SSLCertificateFile "/somewhere/ssl.crt/domain1.crt"
SSLCertificateKeyFile "somewhere/ssl.key/domain1.key"
</VirtualHost>
<VirtualHost 12.34.56.78:1444>
ServerName domain2.com
CustomLog "..."
ErrorLog "..."
SSLEngine on
SSLCertificateFile "/somewhere/ssl.crt/domain2.crt"
SSLCertificateKeyFile "somewhere/ssl.key/domain2.key"
</VirtualHost>
I've just written this from the top of my head, so I don;t know if I didn't
make any syntax errors. But I'll have to try this out someday here, as I'm
going to run into the same problem as you are now.
Greetings,
Krist
______________________________________________________________________
Apache Interface to OpenSSL (mod_ssl) www.modssl.org
User Support Mailing List [EMAIL PROTECTED]
Automated List Manager [EMAIL PROTECTED]
