Date:  Fri, 7 Dec 2007 21:00:09 +0100
From:  Michael Stauber <bq (at mark) solarspeed.net>
Subject:  [coba-e:11373] Re: IP changes for SSL
To:  coba-e (at mark) bluequartz.org
Message-Id:  <200712072100.09594.bq (at mark) solarspeed.net>
In-Reply-To:  <225701c83902$208d2d20$6700a8c0@OfficeKen>
References:  <683F5FB5E2C08E4A8FE8D499A890A3EA0378B7 (at mark) mainserver.mainline.local> <200712071050.07121.bq (at mark) solarspeed.net> <225701c83902$208d2d20$6700a8c0 (at mark) OfficeKen>
X-Mail-Count: 11373

Hi Ken,

> Would it work if with https if
> https://www.someDomain.com
> and
> https://www.someOtherDomain.com
> had separate internal IPs but the same external IP?

When you do NAT, you can of course route port 443 (HTTPS) to another internal 
IP. But if that IP is on the same server as the HTTP version of the site, 
then Apache can get confused a bit as it'll see two sites with the same host 
and domainname. So I'd rather not do that on the same box.

-- 
With best regards,

Michael Stauber