> However, I think the questioner wants to get by with only ONE external
> IP address but many internal SSL hosts. This cannot work because there
> is no way to differentiate packets destined for different internal hosts
> at the SSL level.
what about using stunnel to listen on 443 and then forward decoded traffic to
apache on 80? i came up with that idea a couple of days ago and have yet to test
it if it works at all. the negative point of such setup is that only one
certificate is used for many vhosts, popping up error msgs because domain of
vhost is different than domain certificate is written for. is there a workaround
for that too? :)
--
-----==-
----==-- _
---==---(_)__ __ ____ __ Jure Pecar
--==---/ / _ \/ // /\ \/ / [EMAIL PROTECTED]
-=====/_/_//_/\_._/ /_/\_\
The choice of a GNU generation
______________________________________________________________________
Apache Interface to OpenSSL (mod_ssl) www.modssl.org
User Support Mailing List [EMAIL PROTECTED]
Automated List Manager [EMAIL PROTECTED]
