At 10:52 AM 5/24/2002, you wrote: >"William A. Rowe, Jr." <[EMAIL PROTECTED]> writes: > > > Can I ask WHY? -k has never supported anything but start/stop/restart > > and has always required a seperate -D SSL argument on Win32. > > > > I see the advantage of a simple apachectl doit verb that includes ssl. > > However, overloading -k start -D SSL with -k startssl seems outright > > silly. We can't argue back-compat here, -k didn't exist before. > >I think that this is your main point (please confirm): > > don't support "httpd -k startssl", and instead force the user (or > apachectl) to run "httpd -k startssl -DSSL"
err... still a bit redundant, httpd -k start -DSSL should suffice [I'm pretty sure that's what you ment to ask :-] >One issue that may affect your opinion: historic apachectl verbs are >to be considered deprecated; the vision is that apachectl is just a >wrapper script whose user interface is the same as httpd. Thinking >long-term (e.g., Apache 2.1 or whatever), would you want the user to >have to do > > httpd -k start -DSSL Yes. How many other server modules [protocols especially, such as pop3 and so on] will beg the same. It's bogus. 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." Either the user installs and configures SSL correctly or they don't, I still don't see a benefit in this switch. Uncommenting and Commenting Out our Include ssl.conf should suffice, no? And if a user wants to use the 'classic' mode of toggling a variable [I did so very often when testing both jserv and tomcat, used -D JSERV and -D TOMCAT for that purpose since they can never load together], then do it explicitly before we start seeing -k starttomcat patches popping up everywhere. At 10:57 AM 5/24/2002, JimJag wrote: >But there are tons of configs out there with the IfDef SSL directives >in their httpd.conf file that want/expect/require that SSL >is "defined" Apache 2.0 config files? "Tons" of them? Really :-? Seriously, dump the <IfDefine>. For most cases these should really be <IfModule mod_ssl.c> entities instead anyways. Only the load module itself aught to be caught in an <IfDefine SSL>. I fail to see how setting up ssl in Apache 2.0 should differ from setting up mod_pop3, mod_mbox, mod_jk or any other module. Bill
