On Thu, 2 Sep 1999 [EMAIL PROTECTED] wrote:
> Subject: [BugDB] SSL and Virtual Hosts Question (PR#270)
> 
> Full_Name: Jeff Burdges
> Version: 2.4.0
> OS: Linux
> Submission from: discordia-asy-147.rutgers.edu (128.6.251.147)
> 
> 
> I read the thing in the FAQ about the chicken and the egg problem
> related to having multiple SSL vitual hosts located here:
> 
> http://www.modssl.org/docs/2.4/ssl_faq.html#vhosts
> 
> I see how the chicken and the egg problem exists with SSL directives
> in the virtual host definition, but what I don't see is why those
> directives are in the virtual host definition.  I mean any directive
> which must be the same for multiple SSL enabled virtual hosts (like
> cyphers and stuff) is logically a global directive and (one would
> think) dose not belong in the virtual host part of the SSL set up
> in the first place.. so couldn't all those directives just be made
> global and then still allow multiple SSL enabled virtual hosts
> (they would just be restricted to having the same cyphers and such)
It is irrelevant for name based virtual hosts that is correct, but SSL is
definitely possible for ip based virtual hosts, and as such the
directives do belong in the virtual host definition.

> 
> I suppose things may be this way for backwards compatability of
> config files, but this seems like a big sacrafice.
> 
> Thanks..
> 
> Jeff
> 
> BTW> This is easy to work arround in the site design, but I was
> curious anywho.

-- 
Henrik Olsen,  Dawn Solutions I/S       URL=http://www.iaeste.dk/~henrik/
HAL: I'm evil. (kills astronauts)  Bowman: I must shut you down now, HAL.
HAL: Daisy, Daisy...        Bowman: Now I must finish this mission alone.
(STRANGE THINGS happen, and they MAKE SENSE.)
Reader: Wow. I understand the movie now.      2001, Book-A-Minute version



______________________________________________________________________
Apache Interface to OpenSSL (mod_ssl)                   www.modssl.org
User Support Mailing List                      [EMAIL PROTECTED]
Automated List Manager                            [EMAIL PROTECTED]

Reply via email to