I think you may find that you can only use SSL with IP-based vhosts. For
name-based vhosts you need to have established the connection to read
the Host: header, which for SSL means sending out the appropriate cert
for the domain your client is connecting to. If you only have one IP
interface there's no way that I know to find out what that domain is.
If there _is_ a way I'd love to know about it.
Take care, g-
Gary Carroll, Critical Path Inc.
Dave wrote:
>
> Any ideas on how to specify cert/key files for virtual hosts which do not
> exist?
>
> I am rewriting URLs to the appropriate directories with the following:
>
> RewriteEngine On
> RewriteMap vhost txt:/var/www/conf/vhost.map
> RewriteMap lowercase int:tolower
>
> RewriteCond %{HTTP_HOST} !^$
> RewriteCond ${lowercase:%{HTTP_HOST}|NONE} ^(.+)$
> RewriteCond ${vhost:%1} ^(/.*)$
> RewriteRule ^/(.*)$ %1/$1 [E=VHOST:${lowercase:%{HTTP_HOST}}]
>
> So I do not have any <VirtualHost> entries. Some of these domains I am
> hosting should be SSL enabled. I understand that I can turn on the SSL
> engine in the global config, but how do I specify cert/key files for the
> appropriate domains which need SSL ?
>
> Any help would be greatly appreciated...
>
> -Dave
> California Internet Connection
>
> ______________________________________________________________________
> Apache Interface to OpenSSL (mod_ssl) www.engelschall.com/sw/mod_ssl/
> Official Support Mailing List [EMAIL PROTECTED]
> Automated List Manager [EMAIL PROTECTED]
______________________________________________________________________
Apache Interface to OpenSSL (mod_ssl) www.engelschall.com/sw/mod_ssl/
Official Support Mailing List [EMAIL PROTECTED]
Automated List Manager [EMAIL PROTECTED]
