I certainly see the advantage of having SSL split out into another file.

And indeed, that is the way that I would do it for my own server.  But
the default config file is really there for beginners, not for advanced
users.  Having multiple config files is bad for beginners because it
makes it difficult to answer questions like "where do I put this config
directive?"  It also makes it more difficult to move a specific configuration
from one server to another.  Finally, it is just overall more intimidating
to be faced with a bunch of files to edit, rather than one file that
controls everything.

Having said that, it does look like the overall feeling is that at least
SSL should be split out, and I won't object (strongly).

git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/trunk@91530 13f79535-47bb-0310-9956-ffa450edef68

diff --git a/STATUS b/STATUS
index ec8bb3a25f367cb8e8890204a05778eb387bd6c2..d77a605b17580b7f97bf5a82c44ac106b38d9a05 100644 (file)
--- a/STATUS
+++ b/STATUS
@@ -1,5 +1,5 @@
 APACHE 2.0 STATUS:                                             -*-text-*-
-Last modified at [$Date: 2001/10/17 15:32:22 $]
+Last modified at [$Date: 2001/10/17 15:57:04 $]
 
 Release:
 
@@ -37,7 +37,7 @@ RELEASE SHOWSTOPPERS:
     * The recent split of proxy.conf and ssl.conf, good or bad?
         Split ssl.conf & proxy.conf: +1 OtherBill, Aaron, Ken
         Split out ssl.conf only:     +1 Ryan, BrianH, Jim
-        Everything in httpd.conf:    +1 Cliff, Justin
+        Everything in httpd.conf:    +1 Cliff, Justin, Joshua
 
     * If any request gets to the core handler, without a flag that this 
       r->filename was tested by dir/file_walk, we need to 500 at the very