When a SSL connection is established, the server will only see the IP
address (or IP/Port address), therefore the https request is always
resolved to be for your "main" server. You can either configure multiple IP
addresses or different IP address/Port combinations for multiple SSL sites
on the same machine. You might still have problems with your certificate
though because it also contains the hostname which browsers compare with
the hostname in the actual request, and users get a warning if they don't
match. To get around this problem, you could use wildcard certificates, ie
from Thawte Consulting, for "*.company.com".
Juergen
-----Original Message-----
From: morgan [SMTP:[EMAIL PROTECTED]]
Sent: Wednesday, 21 July 1999 08:04
To: [EMAIL PROTECTED]
Subject: virtual host setup with same certificates
I set up some name based virtual hosts on a linux machine with apache.
I want to get the virtual hosts to use the same certificate as the
"main" server (there is www.company.com as well as blah.company.com
and blahblah.company.com on the same machine) The virtual host part
works fine for all 3, however if I go to https://blah.company.com it
serves up the document root pages for www.company.com instead!??!?!
Yes, DocumentRoot is defined for the each virtual host(it works fine
for http but not for https)
I'm sure this is a (relatively) simple configuration problem, but I
don't know what else to do:( Any help is appreciated.
Morgan
______________________________________________________________________
OpenSSL Project http://www.openssl.org
User Support Mailing List [EMAIL PROTECTED]
Automated List Manager [EMAIL PROTECTED]
______________________________________________________________________
OpenSSL Project http://www.openssl.org
User Support Mailing List [EMAIL PROTECTED]
Automated List Manager [EMAIL PROTECTED]
