Return-Path: Delivered-To: apmail-httpd-dev-archive@httpd.apache.org Received: (qmail 88773 invoked by uid 500); 1 Oct 2001 20:27:26 -0000 Mailing-List: contact dev-help@httpd.apache.org; run by ezmlm Precedence: bulk Reply-To: dev@httpd.apache.org list-help: list-unsubscribe: list-post: Delivered-To: mailing list dev@httpd.apache.org Received: (qmail 88746 invoked from network); 1 Oct 2001 20:27:25 -0000 Date: Mon, 1 Oct 2001 13:27:04 -0700 From: Justin Erenkrantz To: dev@httpd.apache.org Subject: Re: SSL configuration file Message-ID: <20011001132704.S5790@ebuilt.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.3.22.1i X-AntiVirus: scanned for viruses by AMaViS 0.2.1-pre3 (http://amavis.org/) X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N 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. -- justin