Return-Path: Delivered-To: apmail-httpd-dev-archive@httpd.apache.org Received: (qmail 60046 invoked by uid 500); 20 Nov 2001 22:59:09 -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 60035 invoked from network); 20 Nov 2001 22:59:09 -0000 Date: Tue, 20 Nov 2001 14:59:15 -0800 From: Aaron Bannert To: dev@httpd.apache.org Subject: Re: [PATCH] Makefile.in Message-ID: <20011120145915.X18738@clove.org> Mail-Followup-To: Aaron Bannert , dev@httpd.apache.org References: <20011120145433.W18738@clove.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20011120145433.W18738@clove.org> User-Agent: Mutt/1.3.23i X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N On Tue, Nov 20, 2001 at 02:54:33PM -0800, Aaron Bannert wrote: > On Tue, Nov 20, 2001 at 05:46:32PM -0500, MATHIHALLI,MADHUSUDAN (HP-Cupertino,ex1) wrote: > > I have SSL support, but I don't want to bring up the server in SSL mode - > > how do I do that without touching the httpd.conf file ?.. > > It's not going to happen. Everything that is a runtime-configurable > parameter should be controlled by httpd.conf. This slow migration to > command-line parameters is, IMHO, wrong. What happens when I build httpd with SSL support statically? -DSSL would have no effect in that case, and would probably confuse a bunch of people. -aaron