At 06:37 PM 11/2/00 -0500, Clint Gilders wrote:
>Hi All
>
>Newbie Alert!!
>
>Ok... I looked through the archives and found some info on setting up
>ssl and non ssl virtual domains:
<<CLIP>>
> I have set 3 virtual hosts up in a fashion mimicking the above. I
>have "www.perlnerd.com" and "www.dbgrafx.com" set up as non ssl virtual
>domains and "shop.perlnerd.com" set up as my ssl vitual domain. One
>thing I find strange is that the URL https://www.perlnerd.com or
>https://www.dbgrafx.com takes me to the document root of the ssl enabled
>virtual domain while http://www.perlnerd.com etal. takes me to the
>proper document root. Should this be happening?
Yes. The https:// part of the URL causes the browser to make a TCP
connection to port 443 on your server machine. Since your names all
resolve to the same IP address, the request goes to the virtual host.
One solution (I'm sure there are others...) is to set up a separate IP
address (alias) on your box, point the shop.perlnerd.com name to that
address, and adjust your virtual host settings to match.
John Helmuth
[EMAIL PROTECTED]
______________________________________________________________________
Apache Interface to OpenSSL (mod_ssl) www.modssl.org
User Support Mailing List [EMAIL PROTECTED]
Automated List Manager [EMAIL PROTECTED]
