On Fri, Oct 30, 1998, [EMAIL PROTECTED] wrote:
> Nevermind. I confirmed my suspicions that this cannot be done with the
> current implementation of SSL + HTTP/1.1 name based virtual hosts. You
> might want to add this note to your documentation or to a FAQ:
>
> Name-based virtual hosts do not work with SSL/TLS because SSL and TLS
> encrypt all HTTP headers-including the Host header required to
> determine which name-based virtual host is being addressed.
It's in the FAQ, but still only in the FAQ of mod_ssl 2.1.
I'll add it to the 2.0 version, too. Thanks for the hint.
>[...]
> What I don't understand is why this was never fixed in SSL.
Because SSL is not dependent on HTTP. It's a more general protocol over which
you can use more application protocols than HTTP. But ok, you're right. It
could be part of SSL that the client presents the _name_ through which it
resolved the IP over which he is connecting.
Ralf S. Engelschall
[EMAIL PROTECTED]
www.engelschall.com
______________________________________________________________________
Apache Interface to SSLeay (mod_ssl) www.engelschall.com/sw/mod_ssl/
Official Support Mailing List [EMAIL PROTECTED]
Automated List Manager [EMAIL PROTECTED]
