Mailing-List: contact dev-help@httpd.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@httpd.apache.org
Content-Type: text/plain;
  charset="iso-8859-1"
From: Ryan Bloom <rbb@covalent.net>
Reply-To: rbb@covalent.net
Organization: Covalent Technologies
To: dev@httpd.apache.org, Justin Erenkrantz <jerenkrantz@ebuilt.com>
Subject: Re: SSL configuration file
Date: Mon, 1 Oct 2001 13:32:38 -0700
References: <A5374D237E78D41195810090279CC91A05602D95@xcup04.cup.hp.com>
 <20011001132704.S5790@ebuilt.com>
In-Reply-To: <20011001132704.S5790@ebuilt.com>
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
Message-Id: <20011001203239.81BA746DFC@koj.rkbloom.net>

On Monday 01 October 2001 01:27 pm, Justin Erenkrantz wrote:
> On Mon, Oct 01, 2001 at 12:56:40PM -0400, MATHIHALLI,MADHUSUDAN (HP-Cupertino,ex1) wrote:
> > Hi,
> > 	Regarding the SSL configuration, I was wondering if it'd be better
> > to have a separate httpd-ssl.conf file, which contains all the SSL
> > specific information - OR is it better to go with the 1.3 model itself
> > (SSL config in the httpd.conf) ?.. I can send out a patch if required.
>
> The site admin can always do:
>
> Include conf/httpd-ssl.conf
>
> if they wanted to split it out.  No need to do anything else.
>
> IMHO, the example configs should be one file without includes.
> We can leave it up as an exercise to the reader to split it out.

I would prefer to keep the SSL config out of the default config file, because
we aren't going to be distributing binaries with SSL.  At least, I am assuming
we won't, because there are countries that can't download the SSL binaries
legally, and we don't query the user's country at all.

Ryan

______________________________________________________________
Ryan Bloom				rbb@apache.org
Covalent Technologies			rbb@covalent.net
--------------------------------------------------------------