Thanks for the reply.
> If you're using the same SSL configuration and the same certificate for
> both hosts (generally not an option in the real world because of the
> security alert boxes it brings up in the browser), then you won't _notice_
> a problem with namevirtualhost. That's because you're masking the fact
> that both of the vhosts are using the config of ther FIRST one. The fact
> that they're the same means it doesn't matter if they each use their own
> or if they both pick the same one.
They're not the same: they have their respective web trees.
And the server correctly decides which tree to serve. Which
means (in my view) that the server somehow decodes the HOST
header field before it decides which v-host to call.
Does it mean that the server is clever enough to know that all
hosts have the same SSL configuration and to behave accordingly ?
This, however, does not work if I use <VirtualHost 1.2.3.4:443>
(the same IP address for all hosts) instead of <VirtualHost *:443>.
Still a bit confused.
Jan
______________________________________________________________________
Apache Interface to OpenSSL (mod_ssl) www.modssl.org
User Support Mailing List [EMAIL PROTECTED]
Automated List Manager [EMAIL PROTECTED]
