Robin P. Blanchard wrote:
>
> here's the basic scenario:
>
> www.somedomain.com
> www.otherdomain.com (CNAME for www.somedoamin.com)
> www.anotherdomain.com (CNAME for www.somedomain.com)
>
> in my httpd.conf i have
> <VirtualHost www.somedomain.com:80>
> <VirtualHost www.somedomain.com:443>
> <VirtualHost www.otherdomain.com>
> <VirtualHost www.anotherdomain.com>
>
> all, of course, have individual document roots.
> thus, http://www.somedomain.com works perfectly,
> as well as https://www.somedomain.com.
> http://www.otherdomain.com and http://www.anotherdomain.com
> also work fine. however, https://www.otherdomain.com and
> https://www.anotherdomain.com respond as
> https://www.somedomain.com. i don't want these two to
> respond at all to https requests. is there a way to
> accomplish this?
If it were different ip addresses then you could have add this to your
httpd.conf so Apache will only respond to these ip+port combinations:
Listen www.somedomain.com:80
Listen www.somedomain.com:443
Listen www.otherdomain.com
Listen www.anotherdomain.com
Since it are the same however the same ip addresses you will have the
chicken and egg problem as explained in an earlier mail last week.
Maybe the <LocationMatch> can help you if you can check if the full url
is https://www.otherdomain.com or https://www.otherdomain.com and report
an error page? (never worked myself with location match so I'm not
sure.)
David
--
.--.
|o_o |
|:_/ | "One difference between SuSE and Red Hat is that the
// \ \ former operates in a country where people don't sue
(| | ) each other over coffee being too hot."
/'\_ _/`\ Linus Torvalds
\___)=(___/
______________________________________________________________________
Apache Interface to OpenSSL (mod_ssl) www.modssl.org
User Support Mailing List [EMAIL PROTECTED]
Automated List Manager [EMAIL PROTECTED]
