Date:  Sat, 8 Dec 2007 19:22:08 -0800
From:  "Ken Marcus - Precision Web Hosting, Inc." <kenmarcus (at mark) precisionweb.net>
Subject:  [coba-e:11379] Re: IP changes for SSL
To:  <coba-e (at mark) bluequartz.org>
Message-Id:  <009501c83a12$af357e40$6700a8c0@OfficeKen>
References:  <683F5FB5E2C08E4A8FE8D499A890A3EA0378B7 (at mark) mainserver.mainline.local> <200712071050.07121.bq (at mark) solarspeed.net> <225701c83902$208d2d20$6700a8c0 (at mark) OfficeKen> <200712072100.09594.bq (at mark) solarspeed.net>
X-Mail-Count: 11379


----- Original Message ----- 
From: "Michael Stauber" <bq (at mark) solarspeed.net>
To: <coba-e (at mark) bluequartz.org>
Sent: Friday, December 07, 2007 12:00 PM
Subject: [coba-e:11373] Re: IP changes for SSL


> 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
>


Michael

Thanks again for the info.





----
Ken Marcus
Ecommerce Web Hosting by
Precision Web Hosting, Inc.
http://www.precisionweb.net