httpd-cvs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject cvs commit: httpd-2.0 STATUS
Date Wed, 17 Oct 2001 15:57:04 GMT
slive       01/10/17 08:57:04

  Modified:    .        STATUS
  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).
  Revision  Changes    Path
  1.314     +2 -2      httpd-2.0/STATUS
  Index: STATUS
  RCS file: /home/cvs/httpd-2.0/STATUS,v
  retrieving revision 1.313
  retrieving revision 1.314
  diff -u -d -b -u -r1.313 -r1.314
  --- STATUS	2001/10/17 15:32:22	1.313
  +++ STATUS	2001/10/17 15:57:04	1.314
  @@ -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 $]
  @@ -37,7 +37,7 @@
       * 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 

View raw message