httpd-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "MATHIHALLI,MADHUSUDAN (HP-Cupertino,ex1)" <>
Subject RE: [PATCH]
Date Wed, 21 Nov 2001 00:34:46 GMT
-----Original Message-----
From: Ryan Bloom []
On Tuesday 20 November 2001 04:15 pm, Aaron Bannert wrote:
>> I don't understand. Are you saying there are runtime failures if you try
>> to start the server in non-ssl mode while mod_ssl is loaded?  <runs off
>> and builds mod_ssl as a DSO>. Indeed you are correct, but the fact that
>> mod_ssl can't be loaded w/o -DSSL seems like a bug to me.

That's exactly what it should be.. If mod_ssl is compiled as a DSO, it
should not be loaded (at all) unless a -DSSL is given as the command line
option.. If mod_ssl is linked into httpd, then we have no option at all -
which is okay.. But, in anycase, I believe we should be doing something

-> If mod_ssl is DSO,
   <IfDefine SSL>
   LoadModule ssl_module...

-> <IfModule mod_ssl.c>
     include conf/ssl.conf

>> Since it seems that -DSSL and LoadModule ssl_module are mutually
>> I see no reason now to have -DSSL in the first place. If mod_ssl must
>> properly formed runtime directives (ie. in httpd.conf) then why don't we
>> just check <IfModule mod_ssl.c> instead of looking for -DSSL? Please fill
>> me in, because it seems like I've missed something here.
>Just because you load mod_ssl, that doesn't mean you want it enabled.  The
>bug is that mod_ssl is returning errors even if it isn't enabled in any

Exactly !.. 


View raw message