httpd-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "MATHIHALLI,MADHUSUDAN (HP-Cupertino,ex1)" <madhusudan_mathiha...@hp.com>
Subject RE: [PATCH] Makefile.in
Date Tue, 20 Nov 2001 23:18:34 GMT

-----Original Message-----
>From: Aaron Bannert [mailto:aaron@clove.org]
>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.

Okay.. When I build SSL as a DSO, I do get the line "LoadModule
ssl_module..." in my httpd.conf, and all other SSL configuration parameters
ifdef'ed out.. Thus, when I try to bring up Apache (non-SSL mode), I just
can't do it !!.. I'm FORCED to bring up the seve in SSL mode (-DSSL) - which
is not acceptable (to me).. 

If you feel that we should not allow the user to control the startup
behaviour (SSL / non-SSL) by giving command line options, then (IMHO), the
current configuration wrong - the "<IfDefine SSL>..." has to be eliminated
from the httpd.conf and ssl.conf files.. Rather, they should be replaced by
something like "<IfModule mod_ssl>.. " instead.. 



>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.

AFAIK, most of the builds compile SSL as a DSO (because of the
flexibility).. In the case where SSL is built statically, the server SHOULD
come up in SSL mode.. The -DSSL would/should have no effect on the startup
behaviour - which (to me) is perfectly acceptable.. 


-Madhu

Mime
View raw message