Steven J Sobol schrieb:
>
> 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...
It's not intersting, how the vhost is choosen. It's only interesting
that YOU CAN'T USE NAMEBASED VHOSTS. This is a FAQ for both apache-ssl
and mod_ssl. Further discussions should go the the right list (which
would be either [EMAIL PROTECTED] or
[EMAIL PROTECTED]
> > match. To get around this problem, you could use wildcard certificates, ie
> > from Thawte Consulting, for "*.company.com".
>
> Does this work with all browsers?
With Navigator yes, MSIE3 not at all, MSIE4 sometimes, the later the
version the more often.
I never tested opera.
--
Holger Reif Tel.: +49 361 74707-0
SmartRing GmbH Fax.: +49 361 7470720
Europaplatz 5 [EMAIL PROTECTED]
D-99091 Erfurt WWW.SmartRing.de
______________________________________________________________________
OpenSSL Project http://www.openssl.org
User Support Mailing List [EMAIL PROTECTED]
Automated List Manager [EMAIL PROTECTED]
