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.
(From the stronghold documentation).
What I don't understand is why this was never fixed in SSL.
j.
--
Jay Soffian <[EMAIL PROTECTED]> UNIX Systems Administrator
404.572.1941 Cox Interactive Media
______________________________________________________________________
Apache Interface to SSLeay (mod_ssl) www.engelschall.com/sw/mod_ssl/
Official Support Mailing List [EMAIL PROTECTED]
Automated List Manager [EMAIL PROTECTED]
