At 11:18 AM 5/24/2002, you wrote: >On Fri, May 24, 2002 at 11:10:25AM -0500, William A. Rowe, Jr. wrote: > > If you configure your machine for SSL, then run it as SSL already!!! > > Why are we trying to say "you've installed and configured SSL, so now > > you have to turn it on explicitly everytime you start up." Which most > > will take as meaning "I have apache2 installed, so now all I need to do > > is to startssl and everything will work." > >Simple: We have static and dynamic modules. Static modules can't turn >off their LoadModule lines, so we can't use that to turn on and off the >functionality in those modules. -DSSL is the runtime switch that mod_ssl >uses to enable SSL functionality.
That isn't a reason to create -k startssl to duplicate -k start -D SSL ...in fact, if you have a problem with not being able to disable a module in Apache2, then fix the essential problem, which is disabling modules. That was the feature 'broken' in Apache 2. And that still doesn't answer the question, why not simply; #Include conf/ssl.conf And let them uncomment it when they are good and ready. This shouldn't be a constantly toggled decision, either it's ready to run SSL or it's not. Bill
