>
> Based on Plamen's suggestion (thanks, Plamen) I dug out & re-read the
> virtual hosts section of O'Reilly's "Apache: The Definitive Guide" (2nd
> ed) book by the Lauries. They mention use of the 'NameVirtualHost'
> directive & suggest it might be important in controlling access to
> servers under an alternate name. I hadn't been using this directive, so
> I tried it - but the results were identical to what I saw without it;
> i.e.:
>
> https://name1.mydom.com/ ---> index.html file from namessl's doc root
> http://namessl.mydom.com/ ---> index.html file from name1's doc root
>
> The directives I added were:
>
> NameVirtualHost 111.22.33.44:80
> NameVirtualHost 111.22.33.44:443
>
> I don't understand what these directives are supposed to do...
>
> Finally, correct me if I'm wrong, but wouldn't IP-based virtual hosts
> eliminate this problem? Maybe that's the best solution for me since
> I've got a few "extras".
Your NameVirtualHost directive should read:
NameVirtualHost 111.22.33.44
-Dave
______________________________________________________________________
Apache Interface to OpenSSL (mod_ssl) www.modssl.org
User Support Mailing List [EMAIL PROTECTED]
Automated List Manager [EMAIL PROTECTED]
