Mailing-List: contact cvs-help@httpd.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@httpd.apache.org
Date: 17 Oct 2001 15:32:22 -0000
Message-ID: <20011017153222.49361.qmail@icarus.apache.org>
From: jim@apache.org
To: httpd-2.0-cvs@apache.org
Subject: cvs commit: httpd-2.0 STATUS

jim         01/10/17 08:32:22

  Modified:    .        STATUS
  Log:
  Not sure if the number of directives in a normal proxy setup would
  warrant needing a whole separate config file. I see such break outs
  as pretty much dependent on the number of lines it adds to
  httpd.conf... with SSL it makes sense. With proxy, well, I'm not
  sure. To be honest, though, breaking out both won't trouble me
  a bit, but this is my pref.
  
  Revision  Changes    Path
  1.313     +2 -2      httpd-2.0/STATUS
  
  Index: STATUS
  ===================================================================
  RCS file: /home/cvs/httpd-2.0/STATUS,v
  retrieving revision 1.312
  retrieving revision 1.313
  diff -u -r1.312 -r1.313
  --- STATUS	2001/10/17 14:50:48	1.312
  +++ STATUS	2001/10/17 15:32:22	1.313
  @@ -1,5 +1,5 @@
   APACHE 2.0 STATUS:						-*-text-*-
  -Last modified at [$Date: 2001/10/17 14:50:48 $]
  +Last modified at [$Date: 2001/10/17 15:32:22 $]
   
   Release:
   
  @@ -36,7 +36,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
  +        Split out ssl.conf only:     +1 Ryan, BrianH, Jim
           Everything in httpd.conf:    +1 Cliff, Justin
   
       * If any request gets to the core handler, without a flag that this