You are absolutly correct.... SSL protocol is universal - you can
use it for securing mail, pop, imap etc... if virtualhost was
TCP protocol feature.... But it is just a http protocol feature.
In my case when I had not enough ip adresses I used such scheme:

http://secure1.me.ru => https://secure1.me.ru:4301
http://secure2.me.ru => https://secure1.me.ru:4302

and so on... people should not remember port numbers for using secure
sites....
By the way if you use SSL in intranet nothing is wrong that you have
name-based
virtual hosting. The browser will warn you every time that it get wrong
certificate...


With best regards, Yaroslav Rosomakho

----- Original Message -----
From: "Chong, Arthur" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Monday, March 19, 2001 5:29 PM
Subject: RE: SSL with secure/nonsecure virtual hosts


> Hey guys,
>
> I don't think I'm missing it here - but I don't
> think it's possible to do multiple virtual
> named-based hosts on one web server with
> SSL on multiple domains going after port 443.
>
> As I understood it - the SSL layer was at
> a lower level on the stack and all it
> saw was the IP address.
>
> The option to do SSL on other ports was
> do-able but not practical - most firewalls
> filter out other than 80 for http and
> 443 for https.
>
> I was going to see about IP-based virtual
> hosts - but that requires the web server
> to be able to handle multiple IPs going
> against one web server.
>
> Am I wrong in my assumptions?
>
>
> -Arthur.
>
>
>
> -----Original Message-----
> From: Brett W. McCoy [mailto:[EMAIL PROTECTED]]
> Sent: Saturday, March 17, 2001 10:02 AM
> To: [EMAIL PROTECTED]
> Subject: Re: SSL with secure/nonsecure virtual hosts
>
>
> On Sat, 17 Mar 2001, Bob Radvanovsky wrote:
>
> > Hello there!!! I don't have a solution, but am subscribed to the same
list
> > as you (mod_ssl).  I, too, would be interested in knowing more about
> > virtual hosting with more than one domain (yada, yada, yada).  If you
find
> > anything out, I'd appreciate it.  So far, the only reference materials
> that
> > I've found only describe installation/configuration for ONE domain, not
> > multiple, virtual domains.
>
> As long as you aren't using name-based virtual hosts, you can do SSL for
> multiple hosts, otherwise, you're out of luck.  You juts need to set up
> different virtual host sections for what listens on port 80 and what
> listens on port 443 for each virtual host.
>
> -- Brett
> http://www.chapelperilous.net/~bmccoy/
> ------------------------------------------------------------------------
> ... Had this been an actual emergency, we would have fled in terror,
> and you would not have been informed.
>
> ______________________________________________________________________
> Apache Interface to OpenSSL (mod_ssl)                   www.modssl.org
> User Support Mailing List                      [EMAIL PROTECTED]
> Automated List Manager                            [EMAIL PROTECTED]
> ______________________________________________________________________
> Apache Interface to OpenSSL (mod_ssl)                   www.modssl.org
> User Support Mailing List                      [EMAIL PROTECTED]
> Automated List Manager                            [EMAIL PROTECTED]
______________________________________________________________________
Apache Interface to OpenSSL (mod_ssl)                   www.modssl.org
User Support Mailing List                      [EMAIL PROTECTED]
Automated List Manager                            [EMAIL PROTECTED]

Reply via email to