On Wed, Jul 21, 1999 at 09:27:09AM +1200, Juergen Rensen wrote:
> 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.
I have no experience with named SSL virtual hosts sharing an IP, so I might be
off base here, but doesn't the SSL library do a reverse DNS lookup to
determine which site it's running on? so that if 1.2.3.4 resolves back to
www.company.com, but there are other domain names that use that same IP,
the certificate would be running at www.company.com...
> match. To get around this problem, you could use wildcard certificates, ie
> from Thawte Consulting, for "*.company.com".
Does this work with all browsers?
--
North Shore Technologies Corporation http://www.NorthShoreTechnologies.net
We don't just build websites; we build relationships!
815 Superior Ave. #610, Cleveland, OH 44114-2702 216.619.2NET 888.480.4NET
Host of the Forum for Responsible & Ethical E-mail http://www.spamfree.org
______________________________________________________________________
OpenSSL Project http://www.openssl.org
User Support Mailing List [EMAIL PROTECTED]
Automated List Manager [EMAIL PROTECTED]
