cvs commit: apache-1.3/htdocs/manual/misc FAQ.html

1999-05-27 Thread coar 
coar99/05/27 09:49:29

  Modified:htdocs/manual/misc FAQ.html
  Log:
These -1s cause us a lot of grief.  When is a signed int not
a signed int?  When it's an unsigned int or long!  {Sigh}
  
  Revision  ChangesPath
  1.144 +6 -2  apache-1.3/htdocs/manual/misc/FAQ.html
  
  Index: FAQ.html
  ===
  RCS file: /home/cvs/apache-1.3/htdocs/manual/misc/FAQ.html,v
  retrieving revision 1.143
  retrieving revision 1.144
  diff -u -r1.143 -r1.144
  --- FAQ.html  1999/02/21 20:35:12 1.143
  +++ FAQ.html  1999/05/27 16:49:26 1.144
  @@ -14,7 +14,7 @@
 
 Apache Server Frequently Asked Questions
 
  -  $Revision: 1.143 $ ($Date: 1999/02/21 20:35:12 $)
  +  $Revision: 1.144 $ ($Date: 1999/05/27 16:49:26 $)
 
 
 The latest version of this FAQ is always available from the main
  @@ -959,7 +959,11 @@
 Group
 directive (probably in conf/httpd.conf) needs to name a
 group that actually exists in the /etc/group file (or
  -  your system's equivalent).
  +  your system's equivalent).  This problem is also frequently seen when
  +  a negative number is used in the Group directive
  +  (e.g., "Group #-1").  Using a group name
  +  -- not group number -- found in your system's group database should
  +  solve this problem in all cases.

cvs commit: apache-1.3/htdocs/manual/misc FAQ.html

1999-02-21 Thread martin 
martin  99/02/21 12:35:13

  Modified:htdocs/manual/misc FAQ.html
  Log:
  This passage got lost.
  Submitted-By: Joshua Slive <[EMAIL PROTECTED]>
  
  Revision  ChangesPath
  1.143 +39 -1 apache-1.3/htdocs/manual/misc/FAQ.html
  
  Index: FAQ.html
  ===
  RCS file: /export/home/cvs/apache-1.3/htdocs/manual/misc/FAQ.html,v
  retrieving revision 1.142
  retrieving revision 1.143
  diff -u -r1.142 -r1.143
  --- FAQ.html  1999/02/21 00:16:36 1.142
  +++ FAQ.html  1999/02/21 20:35:12 1.143
  @@ -14,7 +14,7 @@
 
 Apache Server Frequently Asked Questions
 
  -  $Revision: 1.142 $ ($Date: 1999/02/21 00:16:36 $)
  +  $Revision: 1.143 $ ($Date: 1999/02/21 20:35:12 $)
 
 
 The latest version of this FAQ is always available from the main
  @@ -1094,6 +1094,44 @@
  http://bugs.apache.org/index/full/2312";>problem report #2312.
  
  
  + 
  +
  + 
  +  I'm using RedHat Linux and I have problems with httpd
  +  dying randomly or not restarting properly
  + 
  +
  +  
  +  RedHat Linux versions 4.x (and possibly earlier) RPMs contain
  +  various nasty scripts which do not stop or restart Apache properly.
  +  These can affect you even if you're not running the RedHat supplied
  +  RPMs.
  +  
  +  
  +  If you're using the default install then you're probably running
  +  Apache 1.1.3, which is outdated.  From RedHat's ftp site you can
  +  pick up a more recent RPM for Apache 1.2.x.  This will solve one of
  +  the problems.
  +  
  +  
  +  If you're using a custom built Apache rather than the RedHat RPMs
  +  then you should rpm -e apache.  In particular you want
  +  the mildly broken /etc/logrotate.d/apache script to be
  +  removed, and you want the broken /etc/rc.d/init.d/httpd
  +  (or httpd.init) script to be removed.  The latter is
  +  actually fixed by the apache-1.2.5 RPMs but if you're building your
  +  own Apache then you probably don't want the RedHat files.
  +  
  +  
  +  We can't stress enough how important it is for folks, especially
  +  vendors to follow the stopping Apache
  +  directions given in our documentation.  In RedHat's defense,
  +  the broken scripts were necessary with Apache 1.1.x because the
  +  Linux support in 1.1.x was very poor, and there were various race
  +  conditions on all platforms.  None of this should be necessary with
  +  Apache 1.2 and later.
  +  
  +

cvs commit: apache-1.3/htdocs/manual/misc FAQ.html

1999-02-21 Thread marc 
marc99/02/20 16:16:37

  Modified:htdocs/manual/misc FAQ.html
  Log:
  Spelling fixes.
  
  Revision  ChangesPath
  1.142 +4 -4  apache-1.3/htdocs/manual/misc/FAQ.html
  
  Index: FAQ.html
  ===
  RCS file: /export/home/cvs/apache-1.3/htdocs/manual/misc/FAQ.html,v
  retrieving revision 1.141
  retrieving revision 1.142
  diff -u -r1.141 -r1.142
  --- FAQ.html  1999/02/20 02:37:44 1.141
  +++ FAQ.html  1999/02/21 00:16:36 1.142
  @@ -14,7 +14,7 @@
 
 Apache Server Frequently Asked Questions
 
  -  $Revision: 1.141 $ ($Date: 1999/02/20 02:37:44 $)
  +  $Revision: 1.142 $ ($Date: 1999/02/21 00:16:36 $)
 
 
 The latest version of this FAQ is always available from the main
  @@ -272,7 +272,7 @@
  
 

  - G. Authentification and Access Restrictions
  + G. Authentication and Access Restrictions
 
  Why isn't restricting access by host or domain name
   working correctly?
  @@ -1427,7 +1427,7 @@
 You may want to check out the Apache Week article
 entitled:
 "http://www.apacheweek.com/features/logfiles"; REL="Help"
  ->Gathering Visitor Information: Customising Your
  +>Gathering Visitor Information: Customizing Your
Logfiles".
 
 
  @@ -1950,7 +1950,7 @@
   
   
   
  -  G. Authentification and Access Restrictions
  +  G. Authentication and Access Restrictions

cvs commit: apache-1.3/htdocs/manual/misc FAQ.html

1999-02-16 Thread coar 
coar99/02/16 07:11:31

  Modified:htdocs/manual/misc FAQ.html
  Log:
Add the licence question to the FAQ..
  
  Revision  ChangesPath
  1.140 +15 -1 apache-1.3/htdocs/manual/misc/FAQ.html
  
  Index: FAQ.html
  ===
  RCS file: /home/cvs/apache-1.3/htdocs/manual/misc/FAQ.html,v
  retrieving revision 1.139
  retrieving revision 1.140
  diff -u -r1.139 -r1.140
  --- FAQ.html  1999/02/14 01:03:18 1.139
  +++ FAQ.html  1999/02/16 15:11:30 1.140
  @@ -14,7 +14,7 @@
 
 Apache Server Frequently Asked Questions
 
  -  $Revision: 1.139 $ ($Date: 1999/02/14 01:03:18 $)
  +  $Revision: 1.140 $ ($Date: 1999/02/16 15:11:30 $)
 
 
 The latest version of this FAQ is always available from the main
  @@ -302,6 +302,9 @@
  
  Why am I getting spam mail from the Apache site?
  
  +   May I include the Apache software on a CD or other
  +package I'm distributing?
  +   
 

   
  @@ -2389,6 +2392,17 @@
  No marketing spam originates from the Apache site.  The only mail
  that comes from the site goes only to addresses that have been
  requested to receive the mail.
  +   
  +   
  +  
  +  May I include the Apache software on a
  +   CD or other package I'm distributing?
  +   
  +   The detailed answer to this question can be found in the
  +   Apache license, which is included in the Apache distribution in
  +   the file LICENSE.  You can also find it on the Web at
  +   http://www.apache.org/LICENSE.txt>.

cvs commit: apache-1.3/htdocs/manual/misc FAQ.html

1999-02-14 Thread lars 
lars99/02/13 17:03:19

  Modified:htdocs/manual/misc FAQ.html
  Log:
  make windoze users happy...
  
  PR: 3860
  Submitted by: Joshua Slive <[EMAIL PROTECTED]>
  
  Revision  ChangesPath
  1.139 +3 -2  apache-1.3/htdocs/manual/misc/FAQ.html
  
  Index: FAQ.html
  ===
  RCS file: /export/home/cvs/apache-1.3/htdocs/manual/misc/FAQ.html,v
  retrieving revision 1.138
  retrieving revision 1.139
  diff -u -r1.138 -r1.139
  --- FAQ.html  1999/02/14 00:45:08 1.138
  +++ FAQ.html  1999/02/14 01:03:18 1.139
  @@ -14,7 +14,7 @@
 
 Apache Server Frequently Asked Questions
 
  -  $Revision: 1.138 $ ($Date: 1999/02/14 00:45:08 $)
  +  $Revision: 1.139 $ ($Date: 1999/02/14 01:03:18 $)
 
 
 The latest version of this FAQ is always available from the main
  @@ -526,7 +526,8 @@
   
  
  Ask in the comp.infosystems.www.servers.unix
  -USENET newsgroup
  +or comp.infosystems.www.servers.ms-windows USENET
  +newsgroup (as appropriate for the platform you use).
   
   A lot of common problems never make it to the bug database because
   there's already high Q&A traffic about them in the

cvs commit: apache-1.3/htdocs/manual/misc FAQ.html

1999-02-14 Thread lars 
lars99/02/13 16:45:09

  Modified:htdocs/manual/misc FAQ.html
  Log:
  Update y2k FAQ.
  
  Revision  ChangesPath
  1.138 +6 -13 apache-1.3/htdocs/manual/misc/FAQ.html
  
  Index: FAQ.html
  ===
  RCS file: /export/home/cvs/apache-1.3/htdocs/manual/misc/FAQ.html,v
  retrieving revision 1.137
  retrieving revision 1.138
  diff -u -r1.137 -r1.138
  --- FAQ.html  1999/02/04 18:15:05 1.137
  +++ FAQ.html  1999/02/14 00:45:08 1.138
  @@ -14,7 +14,7 @@
 
 Apache Server Frequently Asked Questions
 
  -  $Revision: 1.137 $ ($Date: 1999/02/04 18:15:05 $)
  +  $Revision: 1.138 $ ($Date: 1999/02/14 00:45:08 $)
 
 
 The latest version of this FAQ is always available from the main
  @@ -2046,18 +2046,6 @@
 the century is 20 rather than 19.
 
 
  -  Some aspects of Apache's output may use two-digit years, such as the
  -  automatic listing of directory contents provided by
  -  mod_autoindex
  -  with the
  -  FancyIndexing
  -  option enabled, but it is improper to depend upon such displays for
  -  specific syntax.  And even that issue is being addressed by the
  -  developers; a future version of Apache should allow you to format that
  -  display as you like.
  -  
  -  
 Although Apache is Year 2000 compliant, you may still get problems
 if the underlying OS has problems with dates past year 2000
 (e.g., OS calls which accept or return year numbers).
  @@ -2066,6 +2054,11 @@
 the magic boundary to worry about is the year 2038 and not 2000.
 But modern operating systems shouldn't cause any trouble
 at all.
  +  
  +  
  +  Users of Apache 1.2.x should upgrade to a current version of Apache 1.3
  +  (see year-2000 improvements in
  +  Apache 1.3 for details).

cvs commit: apache-1.3/htdocs/manual/misc FAQ.html

1999-02-04 Thread coar 
coar99/02/04 10:15:07

  Modified:htdocs/manual/misc FAQ.html
  Log:
Fix a typo..
  
  PR:   3831
  Submitted by: William Lipp <[EMAIL PROTECTED]>
  Reviewed by:  Ken Coar
  
  Revision  ChangesPath
  1.137 +2 -2  apache-1.3/htdocs/manual/misc/FAQ.html
  
  Index: FAQ.html
  ===
  RCS file: /home/cvs/apache-1.3/htdocs/manual/misc/FAQ.html,v
  retrieving revision 1.136
  retrieving revision 1.137
  diff -u -r1.136 -r1.137
  --- FAQ.html  1999/01/27 03:36:37 1.136
  +++ FAQ.html  1999/02/04 18:15:05 1.137
  @@ -14,7 +14,7 @@
 
 Apache Server Frequently Asked Questions
 
  -  $Revision: 1.136 $ ($Date: 1999/01/27 03:36:37 $)
  +  $Revision: 1.137 $ ($Date: 1999/02/04 18:15:05 $)
 
 
 The latest version of this FAQ is always available from the main
  @@ -1132,7 +1132,7 @@
 Why does Apache send a cookie on every response?

 
  -  Apache does not send automatically send a cookie on every
  +  Apache does not automatically send a cookie on every
 response, unless you have re-compiled it with the
 mod_usertrack
 module, and specifically enabled it with the

cvs commit: apache-1.3/htdocs/manual/misc FAQ.html

1999-01-27 Thread marc 
marc99/01/26 19:36:38

  Modified:htdocs/manual/misc FAQ.html
  Log:
  One item already added by someone sometime, one that should be.
  
  Revision  ChangesPath
  1.136 +2 -3  apache-1.3/htdocs/manual/misc/FAQ.html
  
  Index: FAQ.html
  ===
  RCS file: /export/home/cvs/apache-1.3/htdocs/manual/misc/FAQ.html,v
  retrieving revision 1.135
  retrieving revision 1.136
  diff -u -r1.135 -r1.136
  --- FAQ.html  1998/11/07 00:10:38 1.135
  +++ FAQ.html  1999/01/27 03:36:37 1.136
  @@ -14,7 +14,7 @@
 
 Apache Server Frequently Asked Questions
 
  -  $Revision: 1.135 $ ($Date: 1998/11/07 00:10:38 $)
  +  $Revision: 1.136 $ ($Date: 1999/01/27 03:36:37 $)
 
 
 The latest version of this FAQ is always available from the main
  @@ -79,8 +79,7 @@
   
   
   
  -
  -
  +
   
Background

cvs commit: apache-1.3/htdocs/manual/misc FAQ.html

1998-11-06 Thread lars 
lars98/11/06 09:28:07

  Modified:htdocs/manual/misc FAQ.html
  Log:
  RLimit* vs. premature end of script headers
  
  PR: 3136
  Submitted by: Aaron Digulla
  
  Revision  ChangesPath
  1.134 +7 -1  apache-1.3/htdocs/manual/misc/FAQ.html
  
  Index: FAQ.html
  ===
  RCS file: /home/cvs/apache-1.3/htdocs/manual/misc/FAQ.html,v
  retrieving revision 1.133
  retrieving revision 1.134
  diff -u -r1.133 -r1.134
  --- FAQ.html  1998/10/23 18:46:12 1.133
  +++ FAQ.html  1998/11/06 17:28:05 1.134
  @@ -14,7 +14,7 @@
 
 Apache Server Frequently Asked Questions
 
  -  $Revision: 1.133 $ ($Date: 1998/10/23 18:46:12 $)
  +  $Revision: 1.134 $ ($Date: 1998/11/06 17:28:05 $)
 
 
 The latest version of this FAQ is always available from the main
  @@ -724,6 +724,12 @@
 If your script isn't written in Perl, do the equivalent thing for
 whatever language you are using (e.g., for C, call
 fflush() after writing the headers).
  +  
  +  
  +  Another cause for the "premature end of script headers"
  +  message are the RLimitCPU and RLimitMEM directives. You may
  +  get the message if the CGI script was killed due to a
  +  resource limit.

cvs commit: apache-1.3/htdocs/manual/misc FAQ.html

1998-10-23 Thread coar 
coar98/10/23 11:46:14

  Modified:htdocs/manual/misc FAQ.html
  Log:
Change the FastCGI URL to which the FAQ points; use the
site's main page instead of a stale one.
  
  Submitted by: Marc Mengel <[EMAIL PROTECTED]>
  Reviewed by:  Ken Coar
  
  Revision  ChangesPath
  1.133 +2 -2  apache-1.3/htdocs/manual/misc/FAQ.html
  
  Index: FAQ.html
  ===
  RCS file: /export/home/cvs/apache-1.3/htdocs/manual/misc/FAQ.html,v
  retrieving revision 1.132
  retrieving revision 1.133
  diff -u -r1.132 -r1.133
  --- FAQ.html  1998/10/19 04:59:36 1.132
  +++ FAQ.html  1998/10/23 18:46:12 1.133
  @@ -14,7 +14,7 @@
 
 Apache Server Frequently Asked Questions
 
  -  $Revision: 1.132 $ ($Date: 1998/10/19 04:59:36 $)
  +  $Revision: 1.133 $ ($Date: 1998/10/23 18:46:12 $)
 
 
 The latest version of this FAQ is always available from the main
  @@ -1235,7 +1235,7 @@
 The simple answer is that it was becoming too difficult to keep the
 version being included with Apache synchronized with the master copy
 at the
  -  http://www.fastcgi.com/servers/apache/";
  +  http://www.fastcgi.com/";
 >FastCGI web site.  When a new version of Apache was released, the
 version of the FastCGI module included with it would soon be out of date.

cvs commit: apache-1.3/htdocs/manual/misc FAQ.html

1998-10-19 Thread marc 
marc98/10/18 21:59:40

  Modified:htdocs/manual/misc FAQ.html
  Log:
  Since this entry was based on a small number of reports some time ago
  and current versions of HP's compiler appear to be fine and I haven't
  seen anyone report this in a long time, remove the reference to problems
  with HP's compiler.
  
  Submitted by: Nathaniel McIntosh <[EMAIL PROTECTED]>
  
  Revision  ChangesPath
  1.132 +3 -16 apache-1.3/htdocs/manual/misc/FAQ.html
  
  Index: FAQ.html
  ===
  RCS file: /export/home/cvs/apache-1.3/htdocs/manual/misc/FAQ.html,v
  retrieving revision 1.131
  retrieving revision 1.132
  diff -u -r1.131 -r1.132
  --- FAQ.html  1998/09/30 15:19:00 1.131
  +++ FAQ.html  1998/10/19 04:59:36 1.132
  @@ -14,7 +14,7 @@
 
 Apache Server Frequently Asked Questions
 
  -  $Revision: 1.131 $ ($Date: 1998/09/30 15:19:00 $)
  +  $Revision: 1.132 $ ($Date: 1998/10/19 04:59:36 $)
 
 
 The latest version of this FAQ is always available from the main
  @@ -79,6 +79,8 @@
   
   
   
  +
  +
   
Background
 
  @@ -188,9 +190,6 @@
  
  Why doesn't Apache include SSL?
  
  -   Why do I get core dumps under HPUX using
  -HP's ANSI C compiler?
  -   
  How do I get Apache to send a MIDI file so the
   browser can play it?
  
  @@ -1426,18 +1425,6 @@
 article about
 http://www.apacheweek.com/features/ssl"; REL="Help"
 >Apache and Secure Transactions.
  -  
  -  
  - 
  -
  - 
  -   Why do I get core dumps under HPUX using HP's ANSI
  -   C compiler?
  -  
  -  
  -  We have had numerous reports of Apache dumping core when compiled
  -  with HP's ANSI C compiler using optimization.  Disabling the compiler
  -  optimization has fixed these problems.

cvs commit: apache-1.3/htdocs/manual/misc FAQ.html

1998-09-30 Thread coar 
coar98/09/30 08:19:01

  Modified:htdocs/manual/misc FAQ.html
  Log:
If this isn't a FAQ, I don't know what it is.  And I don't want to
guess.
  
  Revision  ChangesPath
  1.131 +38 -1 apache-1.3/htdocs/manual/misc/FAQ.html
  
  Index: FAQ.html
  ===
  RCS file: /export/home/cvs/apache-1.3/htdocs/manual/misc/FAQ.html,v
  retrieving revision 1.130
  retrieving revision 1.131
  diff -u -r1.130 -r1.131
  --- FAQ.html  1998/09/27 17:36:12 1.130
  +++ FAQ.html  1998/09/30 15:19:00 1.131
  @@ -14,7 +14,7 @@
 
 Apache Server Frequently Asked Questions
 
  -  $Revision: 1.130 $ ($Date: 1998/09/27 17:36:12 $)
  +  $Revision: 1.131 $ ($Date: 1998/09/30 15:19:00 $)
 
 
 The latest version of this FAQ is always available from the main
  @@ -298,6 +298,12 @@
  
  Why am I getting "Expected 
   but saw " when I try to start Apache?
  +   
  +   Why has Apache stolen my favourite site's
  +Internet address?
  +   
  +   Why am I getting spam mail from the Apache site?
  +   
 

   
  @@ -2366,6 +2372,37 @@
  This is a known problem with certain versions of the AIX C compiler.
  IBM are working on a solution, and the issue is being tracked by
  http://bugs.apache.org/index/full/2312";>problem report #2312.
  +   
  +   
  +  
  +  Why has Apache stolen my favourite site's
  +   Internet address?
  +   
  +   The simple answer is: "It hasn't."  This misconception is usually
  +   caused by the site in question having migrated to the Apache Web
  +   server software, but not having migrated the site's content yet.  When
  +   Apache is installed, the default page that gets installed tells the
  +   Webmaster the installation was successful.  The expectation is that
  +   this default page will be replaced with the site's real content.
  +   If it doesn't, complain to the Webmaster, not to the Apache project --
  +   we just make the software and aren't responsible for what people
  +   do (or don't do) with it.
  +   
  +   
  +  
  +  Why am I getting spam mail from the
  +   Apache site?
  +   
  +   The short answer is: "You aren't."  Usually when someone thinks the
  +   Apache site is originating spam, it's because they've traced the
  +   spam to a Web site, and the Web site says it's using Apache.  See the
  +   previous FAQ entry for more details on this
  +   phenomenon.
  +   
  +   
  +   No marketing spam originates from the Apache site.  The only mail
  +   that comes from the site goes only to addresses that have been
  +   requested to receive the mail.

cvs commit: apache-1.3/htdocs/manual/misc FAQ.html

1998-09-27 Thread coar 
coar98/09/27 10:36:13

  Modified:htdocs/manual/misc FAQ.html
  Log:
Add the AIX compiler bug to the FAQ.
  
  PR:   2312, 2534, 2664, 2853, 3042
  
  Revision  ChangesPath
  1.130 +50 -21apache-1.3/htdocs/manual/misc/FAQ.html
  
  Index: FAQ.html
  ===
  RCS file: /export/home/cvs/apache-1.3/htdocs/manual/misc/FAQ.html,v
  retrieving revision 1.129
  retrieving revision 1.130
  diff -u -r1.129 -r1.130
  --- FAQ.html  1998/09/17 14:14:52 1.129
  +++ FAQ.html  1998/09/27 17:36:12 1.130
  @@ -14,7 +14,7 @@
 
 Apache Server Frequently Asked Questions
 
  -  $Revision: 1.129 $ ($Date: 1998/09/17 14:14:52 $)
  +  $Revision: 1.130 $ ($Date: 1998/09/27 17:36:12 $)
 
 
 The latest version of this FAQ is always available from the main
  @@ -296,6 +296,8 @@
  
  How do I submit a patch to the Apache 
Group?
  
  +   Why am I getting "Expected 
  +but saw " when I try to start Apache?
 

   
  @@ -2277,30 +2279,35 @@
  let you apply certain attributes against collections of files or 
resources 
  in very flexible ways - for example, all .gif and .jpg files under
  any "images" directory could be written as /.*\/images\/.*[jpg|gif]/.
  -
  -   The best overview around is probably the one which comes with
  +   
  +   
  +   The best overview around is probably the one which comes with
  Perl.  We implement a simple subset of Perl's regexp support, but
  it's still a good way to learn what they mean.  You can start by
  -   going to the http://www.perl.com/CPAN-local/doc/manual/html/pod/perlre.html#Version_8_Regular_Expresions";>CPAN
  -   page on regular expressions, and branching out from there.
  -
  +   going to the
  +   http://www.perl.com/CPAN-local/doc/manual/html/pod/perlre.html#Version_8_Regular_Expresions";
  +   >CPAN page on regular expressions, and branching out from there.
  +   
 

I'm using gcc and I get some
compilation errors, what is wrong?
  - GCC parses your system header files and produces a modified subset 
which
  +
  +GCC parses your system header files and produces a modified subset which
   it uses for compiling.  This behaviour ties GCC tightly to the version
   of your operating system.  So, for example, if you were running IRIX 5.3
   when you built GCC and then upgrade to IRIX 6.2 later, you will have to
   rebuild GCC.  Similarly for Solaris 2.4, 2.5, or 2.5.1 when you upgrade
   to 2.6.  Sometimes you can type "gcc -v" and it will tell you the version
   of the operating system it was built against.
  +
   
   If you fail to do this, then it is very likely that Apache will fail
   to build.  One of the most common errors is with readv,
   writev, or uio.h.  This is 
not a
   bug with Apache.  You will need to re-install GCC.
  +
  
 
 
  @@ -2313,33 +2320,55 @@
  it covers the directory you are trying to use the .htaccess file in.  
  This is normally accomplished by ensuring it is inside the proper 
  Directory container.
  +   
  
 
 
  How do I submit a patch to the Apache Group?
  
  -   The Apache Group encourages patches from outside developers. There are 2 
main "types"
  -   of patches: small bugfixes and general improvements. Bugfixes should be 
sent to the
  +   The Apache Group encourages patches from outside developers. There are 2
  +   main "types"
  +   of patches: small bugfixes and general improvements. Bugfixes should be
  +   submitting using the
  Apache http://www.apache.org/bug_report.html";>bug report 
page.
  -   Improvements, modifications and additions should follow these 
instructions.
  +   Improvements, modifications, and additions should follow the instructions
  +   below.
  +   
  
  In general, the first course of action is to be a member of the
  -   new-httpd@apache.org mailing list. This indicates to the 
Group that
  -   you are closely following the latest Apache developments. Your patch file 
should be
  -   generated using either 'diff -c' or 'diff -u' 
against the
  -   latest CVS tree. To submit your patch, send Email to 
new-httpd@apache.org
  -   with a Subject: line that starts with [PATCH] 
and
  +   new-httpd@apache.org mailing list. This indicates to the 
Group
  +   that
  +   you are closely following the latest Apache developments. Your patch file
  +   should be
  +   generated using either 'diff -c' or
  +   'diff -u' against the
  +   latest CVS tree. To submit your patch, send email to
  +   new-httpd@apache.org
  +   with a Subject: line that starts with [PATCH] 
and
  includes a general description of the patch. In the body of the message, 
the
  -   patch should be clearly described and then included at the end of the 
message.
  -   If the patch-file is long, you can note a URL

cvs commit: apache-1.3/htdocs/manual/misc FAQ.html

1998-09-09 Thread marc 
marc98/09/09 09:01:05

  Modified:htdocs/manual/misc FAQ.html
  Log:
  Be explicit about the obvious; "if you enable SSIs for a directory
  tree the setting only applies to that directory tree!"
  
  Revision  ChangesPath
  1.127 +16 -1 apache-1.3/htdocs/manual/misc/FAQ.html
  
  Index: FAQ.html
  ===
  RCS file: /export/home/cvs/apache-1.3/htdocs/manual/misc/FAQ.html,v
  retrieving revision 1.126
  retrieving revision 1.127
  diff -u -r1.126 -r1.127
  --- FAQ.html  1998/08/06 20:46:12 1.126
  +++ FAQ.html  1998/09/09 16:01:03 1.127
  @@ -14,7 +14,7 @@
 
 Apache Server Frequently Asked Questions
 
  -  $Revision: 1.126 $ ($Date: 1998/08/06 20:46:12 $)
  +  $Revision: 1.127 $ ($Date: 1998/09/09 16:01:03 $)
 
 
 The latest version of this FAQ is always available from the main
  @@ -126,6 +126,9 @@
  
  How can I have my script output parsed?
  
  +   SSIs don't work for VirtualHosts and/or 
  +user home directories
  +   
  Does or will Apache act as a Proxy server?
  
  What are "multiviews"?
  @@ -829,6 +832,18 @@
 release after 1.3.
 
 
  + 
  +
  + 
  +  SSIs don't work for VirtualHosts and/or 
  +user home directories.
  + 
  +  
  +  This is almost always due to having some setting in your config file that
  +  sets "Options Includes" or some other setting for your DocumentRoot
  +  but not for other directories.  If you set it inside a Directory
  +  section, then that setting will only apply to that directory.  
  +

cvs commit: apache-1.3/htdocs/manual/misc FAQ.html

1998-08-06 Thread jim 
jim 98/08/06 13:46:14

  Modified:htdocs/manual/misc FAQ.html
  Log:
  Some HTML error cleanups (according to DreamWeaver
  AND Alpha and BBEdit) as well as a start of a "how to submit a patch"
  FAQ
  
  Revision  ChangesPath
  1.126 +42 -15apache-1.3/htdocs/manual/misc/FAQ.html
  
  Index: FAQ.html
  ===
  RCS file: /export/home/cvs/apache-1.3/htdocs/manual/misc/FAQ.html,v
  retrieving revision 1.125
  retrieving revision 1.126
  diff -u -r1.125 -r1.126
  --- FAQ.html  1998/08/05 18:04:50 1.125
  +++ FAQ.html  1998/08/06 20:46:12 1.126
  @@ -14,7 +14,7 @@
 
 Apache Server Frequently Asked Questions
 
  -  $Revision: 1.125 $ ($Date: 1998/08/05 18:04:50 $)
  +  $Revision: 1.126 $ ($Date: 1998/08/06 20:46:12 $)
 
 
 The latest version of this FAQ is always available from the main
  @@ -290,6 +290,9 @@
  
  My .htaccess files are being
ignored.
  +   
  +   How do I submit a patch to the Apache 
Group?
  +   
 

   
  @@ -412,7 +415,7 @@
   occasional users.
  
 
  -  
  +  
 

   
  @@ -546,7 +549,7 @@
 (dbx) where

   
  -
  +
   
   (Substitute the appropriate locations for your
   ServerRoot and your httpd and
  @@ -612,7 +615,7 @@
AddHandler cgi-script .cgi

   
  -
  +
   
   The server will then recognize that all files in that location (and
   its logical descendants) that end in ".cgi"
  @@ -624,7 +627,7 @@
   declaration that includes the ExecCGI option.
  
 
  -  
  +  
 
 In some situations, you might not want to actually
 allow all files named "*.cgi" to be executable.
  @@ -646,7 +649,7 @@
 RewriteRule   ^quux\.cgi$  -  [T=application/x-httpd-cgi]

   
  -
  +
  
  Make sure that the directory location is covered by an
   Options
  @@ -654,7 +657,7 @@
   FollowSymLinks option.
  
 
  -  
  +  
 

   
  @@ -697,7 +700,7 @@
   }
  
 
  -  
  +  
 
 This is generally only necessary when you are calling external
 programs from your script that send output to stdout, or if there will
  @@ -758,7 +761,7 @@
AddHandler server-parsed .shtml

   
  -
  +
   
   This indicates that all files ending in ".shtml" in that
   location (or its descendants) should be parsed.  Note that using
  @@ -1177,7 +1180,7 @@
   BrowserMatch JDK/1.0 force-response-1.0
  
 
  -  
  +  
 
 More information about this issue can be found in the
 http://www.apache.org/info/jdk-102.html";
  @@ -1290,7 +1293,7 @@
   This hurts performance and should only be used as a last resort.
  
 
  -  
  +  
 

   
  @@ -1363,7 +1366,7 @@
EXTRA_CFLAGS=-DMAXIMUM_DNS

   
  -
  +
   
   This will cause Apache to be very paranoid about making sure a
   particular host address is really assigned to the name it
  @@ -1441,7 +1444,7 @@
AddType audio/x-midi .mid .midi .kar

   
  -
  +
   
   Note that this may break browsers that do recognize the
   audio/midi MIME type unless they're prepared to also
  @@ -1582,7 +1585,7 @@
   EXTRA_LIBS=-lbind
  
 
  -  
  +  
 

   
  @@ -1692,7 +1695,7 @@
   satisfy any
  
 
  -  
  +  
 
 See the user authentication
 question and the mod_access
  @@ -2295,6 +2298,30 @@
  it covers the directory you are trying to use the .htaccess file in.  
  This is normally accomplished by ensuring it is inside the proper 
  Directory container.
  +   
  +  
  +  
  +   How do I submit a patch to the Apache Group?
  +   
  +   The Apache Group encourages patches from outside developers. There are 2 
main "types"
  +   of patches: small bugfixes and general improvements. Bugfixes should be 
sent to the
  +   Apache http://www.apache.org/bug_report.html";>bug report 
page.
  +   Improvements, modifications and additions should follow these 
instructions.
  +   
  +   In general, the first course of action is to be a member of the
  +   new-httpd@apache.org mailing list. This indicates to the 
Group that
  +   you are closely following the latest Apache developments. Your patch file 
should be
  +   generated using either 'diff -c' or 'diff -u' 
against the
  +   latest CVS tree. To submit your patch, send Email to 
new-httpd@apache.org
  +   with a Subject: line that starts with [PATCH] 
and
  +   includes a general description of the patch. In the body of the message, 
the
  +   patch should be clearly described and then included at the end of the 
message.
  +   If the patch-file is long, you can note a URL to the file instead of the 
file
  +   itself. Use of MIME enclosures/attachments should be avoided.
  +   
  +   Be prepared to respond to any questions

cvs commit: apache-1.3/htdocs/manual/misc FAQ.html

1998-08-05 Thread marc 
marc98/08/05 11:04:54

  Modified:htdocs/manual/misc FAQ.html
  Log:
  Q: "my htaccess files are being ignored"
  A: "yea, Apache listens to you if you tell it to."
  
  Revision  ChangesPath
  1.125 +33 -20apache-1.3/htdocs/manual/misc/FAQ.html
  
  Index: FAQ.html
  ===
  RCS file: /export/home/cvs/apache-1.3/htdocs/manual/misc/FAQ.html,v
  retrieving revision 1.124
  retrieving revision 1.125
  diff -u -r1.124 -r1.125
  --- FAQ.html  1998/07/19 05:30:02 1.124
  +++ FAQ.html  1998/08/05 18:04:50 1.125
  @@ -14,7 +14,7 @@
 
 Apache Server Frequently Asked Questions
 
  -  $Revision: 1.124 $ ($Date: 1998/07/19 05:30:02 $)
  +  $Revision: 1.125 $ ($Date: 1998/08/05 18:04:50 $)
 
 
 The latest version of this FAQ is always available from the main
  @@ -74,7 +74,6 @@
   
   
   
  -
   
   
   
  @@ -286,9 +285,11 @@
  
  What are "regular expressions"?
  
  -   I'm using gcc and I get some compilation 
errors, what
  - is wrong?
  -   
  +   I'm using gcc and I get some compilation 
errors, 
  + what is wrong?
  +   
  +   My .htaccess files are being
  + ignored.
 

   
  @@ -2251,11 +2252,12 @@

 What are "regular expressions"?
  
  -   Regular expressions are a way of describing a pattern - for example, "all 
the words
  -   that begin with the letter A" or "every 10-digit phone number" or even 
"Every sentence
  -   with two commas in it, and no capital letter Q".  Regular expressions 
(aka "regexp"s)
  -   are useful in Apache because they let you apply certain attributes 
against collections
  -   of files or resources in very flexible ways - for example, all .gif and 
.jpg files under
  +   Regular expressions are a way of describing a pattern - for example, "all 
  +   the words that begin with the letter A" or "every 10-digit phone number" 
  +   or even "Every sentence with two commas in it, and no capital letter Q".  
  +   Regular expressions (aka "regexp"s) are useful in Apache because they 
  +   let you apply certain attributes against collections of files or 
resources 
  +   in very flexible ways - for example, all .gif and .jpg files under
  any "images" directory could be written as /.*\/images\/.*[jpg|gif]/.
   
  The best overview around is probably the one which comes with
  @@ -2266,24 +2268,35 @@
  page on regular expressions, and branching out from there.
   
 
  -  
  - I'm using gcc and I get some
  - compilation errors, what is wrong?
  -
  -GCC parses your system header files and produces a modified subset which
  + 
  + I'm using gcc and I get some
  + compilation errors, what is wrong?
  + GCC parses your system header files and produces a modified subset 
which
   it uses for compiling.  This behaviour ties GCC tightly to the version
   of your operating system.  So, for example, if you were running IRIX 5.3
   when you built GCC and then upgrade to IRIX 6.2 later, you will have to
   rebuild GCC.  Similarly for Solaris 2.4, 2.5, or 2.5.1 when you upgrade
   to 2.6.  Sometimes you can type "gcc -v" and it will tell you the version
   of the operating system it was built against.
  -
  +
   If you fail to do this, then it is very likely that Apache will fail
  -to build.  One of the most common errors is with readv,
  -writev, or uio.h.  This is not a
  +to build.  One of the most common errors is with readv,
  +writev, or uio.h.  This is not a
   bug with Apache.  You will need to re-install GCC.
  -   
  -   
  +   
  +  
  +  
  +   My .htaccess files are being 
ignored.
  +   
  +   This is almost always due to your 
  +   AllowOverride directive being set incorrectly for the directory in 
  +   question.  If it is set to None then .htaccess files will 
  +   not even be looked for.  If you do have one that is set, then be certain 
  +   it covers the directory you are trying to use the .htaccess file in.  
  +   This is normally accomplished by ensuring it is inside the proper 
  +   Directory container.
  +   
  +

cvs commit: apache-1.3/htdocs/manual/misc FAQ.html

1998-07-19 Thread marc 
marc98/07/18 22:30:03

  Modified:htdocs/manual/misc FAQ.html
  Log:
  A few minor updates.
  
  Submitted by: Singly Bertrand de (X1995)" <[EMAIL PROTECTED]>
  
  Revision  ChangesPath
  1.124 +5 -5  apache-1.3/htdocs/manual/misc/FAQ.html
  
  Index: FAQ.html
  ===
  RCS file: /export/home/cvs/apache-1.3/htdocs/manual/misc/FAQ.html,v
  retrieving revision 1.123
  retrieving revision 1.124
  diff -u -r1.123 -r1.124
  --- FAQ.html  1998/07/10 00:25:35 1.123
  +++ FAQ.html  1998/07/19 05:30:02 1.124
  @@ -14,7 +14,7 @@
 
 Apache Server Frequently Asked Questions
 
  -  $Revision: 1.123 $ ($Date: 1998/07/10 00:25:35 $)
  +  $Revision: 1.124 $ ($Date: 1998/07/19 05:30:02 $)
 
 
 The latest version of this FAQ is always available from the main
  @@ -260,7 +260,7 @@
  
  Is Apache Year 2000 compliant?
  
  -   I upgraded to Apache 1.3.0 and now my
  +   I upgraded to Apache 1.3 and now my
   virtual hosts don't work!
  
  I'm using RedHat Linux and I have problems with 
httpd
  @@ -380,10 +380,10 @@
 How thoroughly tested is Apache?

 
  -  Apache is run on over 500,000 Internet servers (as of July 1997). It has
  +  Apache is run on over 1.2 million Internet servers (as of July 1998). It 
has
 been tested thoroughly by both developers and users. The Apache Group
 maintains rigorous standards before releasing new versions of their
  -  server, and our server runs without a hitch on over one third of all
  +  server, and our server runs without a hitch on over one half of all
 WWW servers available on the Internet.  When bugs do show up, we
 release patches and new versions as soon as they are available.
 
  @@ -2052,7 +2052,7 @@

   

  -  I upgraded to Apache 1.3.0 and now my virtual hosts don't
  +  I upgraded to Apache 1.3 and now my virtual hosts don't
 work!

cvs commit: apache-1.3/htdocs/manual/misc FAQ.html

1998-07-10 Thread coar 
coar98/07/09 17:25:36

  Modified:htdocs/manual/misc FAQ.html
  Log:
Add a note to the FAQ about increasing file descriptor limits [sic]
on Win95.  Does this have any effect on WinNT?
  
  Submitted by: "The Smiths" <[EMAIL PROTECTED]>
  Reviewed by:  Ken Coar
  
  Revision  ChangesPath
  1.123 +13 -1 apache-1.3/htdocs/manual/misc/FAQ.html
  
  Index: FAQ.html
  ===
  RCS file: /export/home/cvs/apache-1.3/htdocs/manual/misc/FAQ.html,v
  retrieving revision 1.122
  retrieving revision 1.123
  diff -u -r1.122 -r1.123
  --- FAQ.html  1998/07/09 22:02:54 1.122
  +++ FAQ.html  1998/07/10 00:25:35 1.123
  @@ -14,7 +14,7 @@
 
 Apache Server Frequently Asked Questions
 
  -  $Revision: 1.122 $ ($Date: 1998/07/09 22:02:54 $)
  +  $Revision: 1.123 $ ($Date: 1998/07/10 00:25:35 $)
 
 
 The latest version of this FAQ is always available from the main
  @@ -909,6 +909,18 @@
   how to do this is available in the
   performance hints page.  There is a specific
   note for FreeBSD below.
  +
  +For Windows 95, try modifying your C:\CONFIG.SYS file to
  +include a line like
  +
  +
  + FILES=300
  + 
  +
  +
  +Remember that you'll need to reboot your Windows 95 system in order
  +for the new value to take effect.
  +
  
  "Don't do that" - try to run with fewer virtual hosts

cvs commit: apache-1.3/htdocs/manual/misc FAQ.html

1998-07-09 Thread brian 
brian   98/07/09 15:02:55

  Modified:htdocs/manual/misc FAQ.html
  Log:
  We are not public domain.
  
  Revision  ChangesPath
  1.122 +2 -2  apache-1.3/htdocs/manual/misc/FAQ.html
  
  Index: FAQ.html
  ===
  RCS file: /export/home/cvs/apache-1.3/htdocs/manual/misc/FAQ.html,v
  retrieving revision 1.121
  retrieving revision 1.122
  diff -u -r1.121 -r1.122
  --- FAQ.html  1998/06/24 07:18:48 1.121
  +++ FAQ.html  1998/07/09 22:02:54 1.122
  @@ -14,7 +14,7 @@
 
 Apache Server Frequently Asked Questions
 
  -  $Revision: 1.121 $ ($Date: 1998/06/24 07:18:48 $)
  +  $Revision: 1.122 $ ($Date: 1998/07/09 22:02:54 $)
 
 
 The latest version of this FAQ is always available from the main
  @@ -400,7 +400,7 @@

 
 
  -   to continue as a public domain HTTP server,
  +   to continue to be an "open source" no-charge-for-use HTTP server,
  
  to keep up with advances in HTTP protocol and web developments in
   general,

cvs commit: apache-1.3/htdocs/manual/misc FAQ.html

1998-06-24 Thread brian 
brian   98/06/24 00:18:49

  Modified:htdocs/manual/misc FAQ.html
  Log:
  Fix perl variable mention (d'oh!), slightly improve english usage.
  
  Revision  ChangesPath
  1.121 +3 -3  apache-1.3/htdocs/manual/misc/FAQ.html
  
  Index: FAQ.html
  ===
  RCS file: /export/home/cvs/apache-1.3/htdocs/manual/misc/FAQ.html,v
  retrieving revision 1.120
  retrieving revision 1.121
  diff -u -r1.120 -r1.121
  --- FAQ.html  1998/06/07 01:33:52 1.120
  +++ FAQ.html  1998/06/24 07:18:48 1.121
  @@ -14,7 +14,7 @@
 
 Apache Server Frequently Asked Questions
 
  -  $Revision: 1.120 $ ($Date: 1998/06/07 01:33:52 $)
  +  $Revision: 1.121 $ ($Date: 1998/06/24 07:18:48 $)
 
 
 The latest version of this FAQ is always available from the main
  @@ -1244,9 +1244,9 @@
 As of Apache 1.3, CGI scripts are essentially not buffered.  Every time
 your script does a "flush" to output data, that data gets relayed on to
 the client.  Some scripting languages, for example Perl, have their own
  -  buffering for output - this can be disabled by setting the $!
  +  buffering for output - this can be disabled by setting the $|
 special variable to 1.  Of course this does increase the overall number
  -  of packets being transmitted, which can result in a sense of slowness by 
  +  of packets being transmitted, which can result in a sense of slowness for 
 the end user.
 
 Prior to 1.3, you needed to use "nph-" scripts to accomplish 
non-buffering.

cvs commit: apache-1.3/htdocs/manual/misc FAQ.html

1998-06-07 Thread jim 
jim 98/06/06 18:33:57

  Modified:htdocs/manual/misc FAQ.html
  Log:
  Most will ask this when going to 1.3.0
  
  Revision  ChangesPath
  1.120 +3 -3  apache-1.3/htdocs/manual/misc/FAQ.html
  
  Index: FAQ.html
  ===
  RCS file: /export/home/cvs/apache-1.3/htdocs/manual/misc/FAQ.html,v
  retrieving revision 1.119
  retrieving revision 1.120
  diff -u -r1.119 -r1.120
  --- FAQ.html  1998/06/06 15:39:26 1.119
  +++ FAQ.html  1998/06/07 01:33:52 1.120
  @@ -14,7 +14,7 @@
 
 Apache Server Frequently Asked Questions
 
  -  $Revision: 1.119 $ ($Date: 1998/06/06 15:39:26 $)
  +  $Revision: 1.120 $ ($Date: 1998/06/07 01:33:52 $)
 
 
 The latest version of this FAQ is always available from the main
  @@ -260,7 +260,7 @@
  
  Is Apache Year 2000 compliant?
  
  -   I upgraded to Apache 1.3b and now my
  +   I upgraded to Apache 1.3.0 and now my
   virtual hosts don't work!
  
  I'm using RedHat Linux and I have problems with 
httpd
  @@ -2040,7 +2040,7 @@

   

  -  I upgraded to Apache 1.3b and now my virtual hosts don't
  +  I upgraded to Apache 1.3.0 and now my virtual hosts don't
 work!

cvs commit: apache-1.3/htdocs/manual/misc FAQ.html

1998-06-06 Thread brian 
brian   98/06/06 08:39:27

  Modified:htdocs/manual/misc FAQ.html
  Log:
  PR: 2365
  
  Updated certain questions for 1.3 - simplicity is always a good idea.
  
  Revision  ChangesPath
  1.119 +16 -63apache-1.3/htdocs/manual/misc/FAQ.html
  
  Index: FAQ.html
  ===
  RCS file: /export/home/cvs/apache-1.3/htdocs/manual/misc/FAQ.html,v
  retrieving revision 1.118
  retrieving revision 1.119
  diff -u -r1.118 -r1.119
  --- FAQ.html  1998/05/30 01:27:25 1.118
  +++ FAQ.html  1998/06/06 15:39:26 1.119
  @@ -14,7 +14,7 @@
 
 Apache Server Frequently Asked Questions
 
  -  $Revision: 1.118 $ ($Date: 1998/05/30 01:27:25 $)
  +  $Revision: 1.119 $ ($Date: 1998/06/06 15:39:26 $)
 
 
 The latest version of this FAQ is always available from the main
  @@ -1091,19 +1091,15 @@
 
 Apache does not send automatically send a cookie on every
 response, unless you have re-compiled it with the
  -  mod_cookies
  -  module.
  -  This module was distributed with Apache prior to 1.2.
  -  This module may help track users, and uses cookies to do this. If
  -  you are not using the data generated by mod_cookies, do
  -  not compile it into Apache. Note that in 1.2 this module was renamed
  -  to the more correct name
  -  mod_usertrack,
  -  and cookies
  -  have to be specifically enabled with the
  +  mod_usertrack
  +  module, and specifically enabled it with the
 CookieTracking
 directive.
  +  This module has been in Apache since version 1.2.
  +  This module may help track users, and uses cookies to do this. If
  +  you are not using the data generated by mod_usertrack, do
  +  not compile it into Apache. 
 
 

  @@ -1244,60 +1240,17 @@
 How can I get my script's output without Apache buffering
 it?  Why doesn't my server push work?

  -  
  -  In order to improve network performance, Apache buffers script output
  -  into relatively large chunks.  If you have a script that sends
  -  information in bursts (eg. as partial-done messages in a multi-commit
  -  database transaction or any type of server push), the client will 
  -  not necessarily get the output as the script is generating it.
  -  
  -  
  -  To avoid this, Apache recognizes scripts whose names begin with
  -  "nph-" as non-parsed-header scripts.
  -  That is, Apache won't buffer their output, but connect it directly to
  -  the socket going back to the client.
  -  
  -  
  -  While this will probably do what you want, there are some
  -  disadvantages to it:
  -  
  -  
  -   YOU (the script) are responsible for generating
  - ALL of the HTTP headers, and no longer
  - just the "Content-type" or
  - "Location" headers
  -   
  -   Unless your script generates its output carefully, you will see a
  -performance penalty as excessive numbers of packets go back and forth
  -   
  -  
  -  
  -  As an example how you might handle the former (in a Perl script):
  -  
  -  
  -  
  -   if ($0 =~ m:^(.*/)*nph-[^/]*$:) {
  -
  -
  -$HTTP_headers = 
  -"HTTP/1.1 200 OK\015\012";
  -
  -
  -$HTTP_headers .= 
  -"Connection: close\015\012";
  -
  -
  -print $HTTP_headers;
  -
  -}
  -   
  -  
  -  
 
  -  and then follow with your normal non-nph headers.
  +  As of Apache 1.3, CGI scripts are essentially not buffered.  Every time
  +  your script does a "flush" to output data, that data gets relayed on to
  +  the client.  Some scripting languages, for example Perl, have their own
  +  buffering for output - this can be disabled by setting the $!
  +  special variable to 1.  Of course this does increase the overall number
  +  of packets being transmitted, which can result in a sense of slowness by 
  +  the end user.
 
  -  Note that in version 1.3, all CGI scripts will be unbuffered
  -  so the only difference between nph scripts and normal scripts is
  +  Prior to 1.3, you needed to use "nph-" scripts to accomplish 
non-buffering.
  +  Today, the only difference between nph scripts and normal scripts is
 that nph scripts require the full HTTP headers to be sent.

cvs commit: apache-1.3/htdocs/manual/misc FAQ.html

1998-05-30 Thread coar 
coar98/05/29 18:27:26

  Modified:htdocs/manual/misc FAQ.html
  Log:
Add a note to the FAQ about something that should maybe be added
at some point.  (Hidden in an HTML comment.)
  
  PR:   2300
  
  Revision  ChangesPath
  1.118 +3 -1  apache-1.3/htdocs/manual/misc/FAQ.html
  
  Index: FAQ.html
  ===
  RCS file: /export/home/cvs/apache-1.3/htdocs/manual/misc/FAQ.html,v
  retrieving revision 1.117
  retrieving revision 1.118
  diff -u -r1.117 -r1.118
  --- FAQ.html  1998/05/25 17:35:26 1.117
  +++ FAQ.html  1998/05/30 01:27:25 1.118
  @@ -14,7 +14,7 @@
 
 Apache Server Frequently Asked Questions
 
  -  $Revision: 1.117 $ ($Date: 1998/05/25 17:35:26 $)
  +  $Revision: 1.118 $ ($Date: 1998/05/30 01:27:25 $)
 
 
 The latest version of this FAQ is always available from the main
  @@ -78,6 +78,8 @@
   
   
   
  +
  +
   
Background

cvs commit: apache-1.3/htdocs/manual/misc FAQ.html

1998-05-25 Thread dgaudet 
dgaudet 98/05/25 10:35:29

  Modified:htdocs/manual/misc FAQ.html
  Log:
  document the all too common gcc version mismatch
  
  Revision  ChangesPath
  1.117 +21 -1 apache-1.3/htdocs/manual/misc/FAQ.html
  
  Index: FAQ.html
  ===
  RCS file: /export/home/cvs/apache-1.3/htdocs/manual/misc/FAQ.html,v
  retrieving revision 1.116
  retrieving revision 1.117
  diff -u -r1.116 -r1.117
  --- FAQ.html  1998/05/20 14:22:39 1.116
  +++ FAQ.html  1998/05/25 17:35:26 1.117
  @@ -14,7 +14,7 @@
 
 Apache Server Frequently Asked Questions
 
  -  $Revision: 1.116 $ ($Date: 1998/05/20 14:22:39 $)
  +  $Revision: 1.117 $ ($Date: 1998/05/25 17:35:26 $)
 
 
 The latest version of this FAQ is always available from the main
  @@ -284,6 +284,9 @@
  
  What are "regular expressions"?
  
  +   I'm using gcc and I get some compilation 
errors, what
  + is wrong?
  +   
 

   
  @@ -2297,6 +2300,23 @@
   
 
 
  + I'm using gcc and I get some
  + compilation errors, what is wrong?
  +
  +GCC parses your system header files and produces a modified subset which
  +it uses for compiling.  This behaviour ties GCC tightly to the version
  +of your operating system.  So, for example, if you were running IRIX 5.3
  +when you built GCC and then upgrade to IRIX 6.2 later, you will have to
  +rebuild GCC.  Similarly for Solaris 2.4, 2.5, or 2.5.1 when you upgrade
  +to 2.6.  Sometimes you can type "gcc -v" and it will tell you the version
  +of the operating system it was built against.
  +
  +If you fail to do this, then it is very likely that Apache will fail
  +to build.  One of the most common errors is with readv,
  +writev, or uio.h.  This is not a
  +bug with Apache.  You will need to re-install GCC.
  +   
  +

cvs commit: apache-1.3/htdocs/manual/misc FAQ.html

1998-05-20 Thread brian 
brian   98/05/20 04:12:43

  Modified:htdocs/manual/misc FAQ.html
  Log:
  Added text about regualr expressions.
  
  Revision  ChangesPath
  1.115 +23 -1 apache-1.3/htdocs/manual/misc/FAQ.html
  
  Index: FAQ.html
  ===
  RCS file: /export/home/cvs/apache-1.3/htdocs/manual/misc/FAQ.html,v
  retrieving revision 1.114
  retrieving revision 1.115
  diff -u -r1.114 -r1.115
  --- FAQ.html  1998/05/05 05:09:31 1.114
  +++ FAQ.html  1998/05/20 11:12:42 1.115
  @@ -15,7 +15,7 @@
 
 Apache Server Frequently Asked Questions
 
  -  $Revision: 1.114 $ ($Date: 1998/05/05 05:09:31 $)
  +  $Revision: 1.115 $ ($Date: 1998/05/20 11:12:42 $)
 
 
 The latest version of this FAQ is always available from the main
  @@ -283,6 +283,8 @@
  What's the best hardware/operating system/... How do
   I get the most out of my Apache Web server?
  
  +   What are "regular expressions"?
  +   
 

   
  @@ -2277,6 +2279,26 @@
 
 

  + 
  +  What are "regular expressions"?
  +   
  +   Regular expressions are a way of describing a pattern - for example, "all 
the words
  +   that begin with the letter A" or "every 10-digit phone number" or even 
"Every sentence
  +   with two commas in it, and no capital letter Q".  Regular expressions 
(aka "regexp"s)
  +   are useful in Apache because they let you apply certain attributes 
against collections
  +   of files or resources in very flexible ways - for example, all .gif and 
.jpg files under
  +   any "images" directory could be written as /.*\/images\/.*[jpg|gif]/.
  +
  +   The best overview around is probably the one which comes with
  +   Perl.  We implement a simple subset of Perl's regexp support, but
  +   it's still a good way to learn what they mean.  You can start by
  +   going to the http://www.perl.com/CPAN-local/doc/manual/html/pod/perlre.html#Version_8_Regular_Expresions";>CPAN
  +   page on regular expressions, and branching out from there.
  +
  +  
  +  
  +

cvs commit: apache-1.3/htdocs/manual/misc FAQ.html

1998-05-05 Thread brian 
brian   98/05/04 22:09:32

  Modified:htdocs/manual/misc FAQ.html
  Log:
  Slightly improve the grammar; however, in my opinion this whole chunk can just
  be tossed out of the FAQ.  I can't believe we're actually asked "how can I 
make
  only one file executable?".
  
  Revision  ChangesPath
  1.114 +2 -2  apache-1.3/htdocs/manual/misc/FAQ.html
  
  Index: FAQ.html
  ===
  RCS file: /export/home/cvs/apache-1.3/htdocs/manual/misc/FAQ.html,v
  retrieving revision 1.113
  retrieving revision 1.114
  diff -u -r1.113 -r1.114
  --- FAQ.html  1998/04/25 18:48:43 1.113
  +++ FAQ.html  1998/05/05 05:09:31 1.114
  @@ -15,7 +15,7 @@
 
 Apache Server Frequently Asked Questions
 
  -  $Revision: 1.113 $ ($Date: 1998/04/25 18:48:43 $)
  +  $Revision: 1.114 $ ($Date: 1998/05/05 05:09:31 $)
 
 
 The latest version of this FAQ is always available from the main
  @@ -619,7 +619,7 @@
 
 
 
  -  In some situations it can be not conform to your local policy to actually
  +  In some situations, you might not want to actually
 allow all files named "*.cgi" to be executable.
 Perhaps all you want is to enable a particular file in a normal directory 
to
 be executable. This can be alternatively accomplished

cvs commit: apache-1.3/htdocs/manual/misc FAQ.html

1998-04-25 Thread marc 
marc98/04/25 11:48:44

  Modified:htdocs/manual/misc FAQ.html
  Log:
  It is bogus to direct people only to .unix for the Win32 version.
  
  Revision  ChangesPath
  1.113 +7 -5  apache-1.3/htdocs/manual/misc/FAQ.html
  
  Index: FAQ.html
  ===
  RCS file: /export/home/cvs/apache-1.3/htdocs/manual/misc/FAQ.html,v
  retrieving revision 1.112
  retrieving revision 1.113
  diff -u -r1.112 -r1.113
  --- FAQ.html  1998/04/16 15:36:51 1.112
  +++ FAQ.html  1998/04/25 18:48:43 1.113
  @@ -15,7 +15,7 @@
 
 Apache Server Frequently Asked Questions
 
  -  $Revision: 1.112 $ ($Date: 1998/04/16 15:36:51 $)
  +  $Revision: 1.113 $ ($Date: 1998/04/25 18:48:43 $)
 
 
 The latest version of this FAQ is always available from the main
  @@ -419,10 +419,12 @@
 http://www.apache.org/bug_report.html";>the bug report page.
 Other questions should be directed to the
 news:comp.infosystems.www.servers.unix";
  -  >comp.infosystems.www.servers.unix
  -  newsgroup, where some of the Apache team lurk,
  -  in the company of many other httpd gurus who should be able
  -  to help.
  +  >comp.infosystems.www.servers.unix or news:comp.infosystems.www.servers.ms-windows";
  +  >comp.infosystems.www.servers.ms-windows
  +  newsgroup (as appropriate for the platform you use), where some of the 
  +  Apache team lurk, in the company of many other httpd gurus who 
  +  should be able to help.
 
 
 Commercial support for Apache is, however, available from a number

cvs commit: apache-1.3/htdocs/manual/misc FAQ.html

1998-04-16 Thread marc 
marc98/04/16 08:36:54

  Modified:htdocs/manual/misc FAQ.html
  Log:
  Someone should add disable-auth-for-subdir hack.
  
  Revision  ChangesPath
  1.112 +3 -1  apache-1.3/htdocs/manual/misc/FAQ.html
  
  Index: FAQ.html
  ===
  RCS file: /export/home/cvs/apache-1.3/htdocs/manual/misc/FAQ.html,v
  retrieving revision 1.111
  retrieving revision 1.112
  diff -u -r1.111 -r1.112
  --- FAQ.html  1998/04/11 06:34:23 1.111
  +++ FAQ.html  1998/04/16 15:36:51 1.112
  @@ -15,7 +15,7 @@
 
 Apache Server Frequently Asked Questions
 
  -  $Revision: 1.111 $ ($Date: 1998/04/11 06:34:23 $)
  +  $Revision: 1.112 $ ($Date: 1998/04/16 15:36:51 $)
 
 
 The latest version of this FAQ is always available from the main
  @@ -77,6 +77,8 @@
   
   
   
  +
  +
   
Background

cvs commit: apache-1.3/htdocs/manual/misc FAQ.html

1998-04-11 Thread marc 
marc98/04/10 23:34:25

  Modified:htdocs/manual/misc FAQ.html
  Log:
  Fix FAQ entry on problems with POST, plus a few cleanups.  The old
  entry is extremely misleading, and answering a Q that isn't really FA,
  and I see someone posting somewhere every week who tries this to
  fix their "method not allowed" problems.
  
  Revision  ChangesPath
  1.111 +19 -33apache-1.3/htdocs/manual/misc/FAQ.html
  
  Index: FAQ.html
  ===
  RCS file: /export/home/cvs/apache-1.3/htdocs/manual/misc/FAQ.html,v
  retrieving revision 1.110
  retrieving revision 1.111
  diff -u -r1.110 -r1.111
  --- FAQ.html  1998/03/27 01:56:34 1.110
  +++ FAQ.html  1998/04/11 06:34:23 1.111
  @@ -15,7 +15,7 @@
 
 Apache Server Frequently Asked Questions
 
  -  $Revision: 1.110 $ ($Date: 1998/03/27 01:56:34 $)
  +  $Revision: 1.111 $ ($Date: 1998/04/11 06:34:23 $)
 
 
 The latest version of this FAQ is always available from the main
  @@ -134,8 +134,8 @@
  Can I increase FD_SETSIZE
   on FreeBSD?
  
  -   Why do I keep getting "access denied" 
for
  -form POST requests?
  +   Why do I keep getting "Method Not 
  +Allowed" for form POST requests?
  
  Can I use my /etc/passwd file
   for Web page authentication?
  @@ -964,32 +964,18 @@
 

   
  - 
  -  Why do I keep getting "access denied" for form POST
  -  requests?
  + 
  +  Why do I keep getting "Method Not Allowed" for 
  +  form POST requests?

 
  -  The most common cause of this is a  section
  -  that only names the GET method.  Look in your
  -  configuration files for something that resembles the following and
  -  would affect the location where the POST-handling script resides:
  +  This is almost always due to Apache not being configured to treat the
  +  file you are trying to POST to as a CGI script.  You can not POST 
  +  to a normal HTML file; the operation has no meaning.  See the FAQ 
  +  entry on CGIs outside ScriptAliased
  +  directories for details on how to configure Apache to treat the
  +  file in question as a CGI.
 
  -  
  -  
  -   
  -:
  -   
  -  
  -  
  -  
  -  Change that to  and the 
problem
  -  will probably go away.  Better yet, remove the
  -   and  lines
  -  altogether unless you're specifically trying to limit by
  -  method (GET, PUT, et cetera).  If
  -  you don't have a  container, the
  -  restrictions apply equally to all methods.
  -  
 

   
  @@ -2143,10 +2129,10 @@

   
 
  -  RedHat Linux versions 4.x (and possibly earlier) rpms contain
  +  RedHat Linux versions 4.x (and possibly earlier) RPMs contain
 various nasty scripts which do not stop or restart Apache properly.
 These can affect you even if you're not running the RedHat supplied
  -  rpms.
  +  RPMs.
 
 
 If you're using the default install then you're probably running
  @@ -2155,12 +2141,12 @@
 the problems.
 
 
  -  If you're using a custom built Apache rather than the RedHat rpms
  +  If you're using a custom built Apache rather than the RedHat RPMs
 then you should rpm -e apache.  In particular you want
 the mildly broken /etc/logrotate.d/apache script to be
 removed, and you want the broken /etc/rc.d/init.d/httpd
 (or httpd.init) script to be removed.  The latter is
  -  actually fixed by the apache-1.2.5 rpms but if you're building your
  +  actually fixed by the apache-1.2.5 RPMs but if you're building your
 own Apache then you probably don't want the RedHat files.
 
 
  @@ -2250,12 +2236,12 @@
   
 
 These are symptoms of a fine locking problem, which usually means that
  -  the server is trying to use a synchronisation file on an NFS filesystem.
  +  the server is trying to use a synchronization file on an NFS filesystem.
 
 
 Because of its parallel-operation model, the Apache Web server needs to
  -  provide some form of synchronisation when accessing certain resources.
  -  One of these synchronisation methods involves taking out locks on a file,
  +  provide some form of synchronization when accessing certain resources.
  +  One of these synchronization methods involves taking out locks on a file,
 which means that the filesystem whereon the lockfile resides must support
 locking.  In many cases this means it can't be kept on an
 NFS-mounted filesystem.

cvs commit: apache-1.3/htdocs/manual/misc FAQ.html

1998-03-27 Thread coar 
coar98/03/26 17:56:35

  Modified:htdocs/manual/misc FAQ.html
  Log:
Sort-of FAQ: "how do I make Apache scream?"
  
  Submitted by: jim <[EMAIL PROTECTED]>
  
  Revision  ChangesPath
  1.110 +16 -2 apache-1.3/htdocs/manual/misc/FAQ.html
  
  Index: FAQ.html
  ===
  RCS file: /export/home/cvs/apache-1.3/htdocs/manual/misc/FAQ.html,v
  retrieving revision 1.109
  retrieving revision 1.110
  diff -u -r1.109 -r1.110
  --- FAQ.html  1998/03/24 02:58:49 1.109
  +++ FAQ.html  1998/03/27 01:56:34 1.110
  @@ -15,7 +15,7 @@
 
 Apache Server Frequently Asked Questions
 
  -  $Revision: 1.109 $ ($Date: 1998/03/24 02:58:49 $)
  +  $Revision: 1.110 $ ($Date: 1998/03/27 01:56:34 $)
 
 
 The latest version of this FAQ is always available from the main
  @@ -132,7 +132,7 @@
   virtual hosts?
  
  Can I increase FD_SETSIZE
  -on FreeBSD?
  +on FreeBSD?
  
  Why do I keep getting "access denied" 
for
   form POST requests?
  @@ -278,6 +278,9 @@
   fills with "fcntl: F_SETLKW: No record locks
   available" or similar messages
  
  +   What's the best hardware/operating system/... How do
  +I get the most out of my Apache Web server?
  +   
 

   
  @@ -2270,6 +2273,17 @@
 /var/tmp).
 See the LockFile
 documentation for more information.
  +  
  +  
  + 
  + 
  +  What's the best hardware/operating system/... How do
  +  I get the most out of my Apache Web server?
  + 
  +  
  +  Check out Dean Gaudet's
  +  http://www.apache.org/docs/misc/perf-tuning.html";
  +  >performance tuning page.

cvs commit: apache-1.3/htdocs/manual/misc FAQ.html

1998-03-24 Thread coar 
coar98/03/23 18:58:51

  Modified:htdocs/manual/misc FAQ.html
  Log:
Time for some FAQ revamp work.  Mostly cosmetic, but the LockFile
issue has been added because it has certainly become a FAQ!
  
  Revision  ChangesPath
  1.109 +403 -396  apache-1.3/htdocs/manual/misc/FAQ.html
  
  Index: FAQ.html
  ===
  RCS file: /export/home/cvs/apache-1.3/htdocs/manual/misc/FAQ.html,v
  retrieving revision 1.108
  retrieving revision 1.109
  diff -u -r1.108 -r1.109
  --- FAQ.html  1998/02/18 21:07:25 1.108
  +++ FAQ.html  1998/03/24 02:58:49 1.109
  @@ -15,7 +15,7 @@
 
 Apache Server Frequently Asked Questions
 
  -  $Revision: 1.108 $ ($Date: 1998/02/18 21:07:25 $)
  +  $Revision: 1.109 $ ($Date: 1998/03/24 02:58:49 $)
 
 
 The latest version of this FAQ is always available from the main
  @@ -109,7 +109,7 @@
   work?"  What to do in case of problems
  
  How compatible is Apache with my existing
  -NCSA 1.3 setup?
  +NCSA 1.3 setup?
  
  How do I enable CGI execution
   in directories other than the ScriptAlias?
  @@ -129,149 +129,155 @@
  What are "multiviews"?
  
  Why can't I run more than 
  -virtual hosts?
  +virtual hosts?
  
  -   Can I increase FD_SETSIZE on FreeBSD?
  +   Can I increase FD_SETSIZE
  +on FreeBSD?
  
  Why do I keep getting "access denied" 
for
  -form POST requests?
  +form POST requests?
  
  Can I use my /etc/passwd file
  -for Web page authentication?
  +for Web page authentication?
  
  Why doesn't my ErrorDocument
  -401 work?
  +401 work?
  
  How can I use ErrorDocument
  -   and SSI to simplify customized error messages?
  +and SSI to simplify customized error messages?
  
  Why do I get "setgid: Invalid
  -argument" at startup?
  +argument" at startup?
  
  Why does Apache send a cookie on every 
response?
  
  Why don't my cookies work, I even compiled in
  -mod_cookies?
  +mod_cookies?
  
  Why do my Java app[let]s give me plain 
text
  -when I request an URL from an Apache server?
  +when I request an URL from an Apache server?
  
  Why can't I publish to my Apache server
  -using PUT on Netscape Gold and other programs?
  +using PUT on Netscape Gold and other programs?
  
  Why isn't FastCGI included with Apache any
  -more?
  +more?
  
  Why am I getting "httpd: could not
  -set socket option TCP_NODELAY" in my error log?
  +set socket option TCP_NODELAY" in my error log?
  
  Why am I getting "connection
  -reset by peer" in my error log?
  +reset by peer" in my error log?
  
  How can I get my script's output without
  -Apache buffering it?  Why doesn't my server push work?
  +Apache buffering it?  Why doesn't my server push work?
  
  Why do I get complaints about redefinition
  -of "struct iovec" when compiling under Linux?
  +of "struct iovec" when compiling under 
Linux?
  
  The errorlog says Apache dumped core,
  -but where's the dump file?
  +but where's the dump file?
  
  Why isn't restricting access by host or domain name
  -working correctly?
  +working correctly?
  
  Why doesn't Apache include SSL?
  
  Why do I get core dumps under HPUX using
  -HP's ANSI C compiler?
  +HP's ANSI C compiler?
  
  How do I get Apache to send a MIDI file so the
  -browser can play it?
  +browser can play it?
  
  Why won't Apache compile with my
  -system's cc?
  +system's cc?
  
  -   How do I add browsers and referrers to my
  -logs?
  +   How do I add browsers and referrers to my logs?
  
  Why do I get an error about an undefined
  -reference to "__inet_ntoa" or other
  -__inet_* symbols?
  +reference to "__inet_ntoa" or other
  +__inet_* symbols?
  
  Why does accessing directories only work
  -when I include the trailing "/"
  -(e.g., http://foo.domain.com/~user/) but
  -not when I omit it
  -(e.g., http://foo.domain.com/~user)?
  +when I include the trailing "/"
  +(e.g., http://foo.domain.com/~user/) but
  +not when I omit it
  +(e.g., http://foo.domain.com/~user)?
  
  How do I set up Apache to require
  -a username and password to access certain documents?
  +a username and password to access certain documents?
  
  Why is the environment variable
  -   REMOTE_USER not set?
  +REMOTE_USER not set?
  
  How do I set up Apache to allow access
  -to certain documents only if a site is either a local site
  -or the user supplies a password and username?
  +

cvs commit: apache-1.3/htdocs/manual/misc FAQ.html

1998-02-18 Thread dgaudet 
dgaudet 98/02/18 13:07:26

  Modified:htdocs/manual/misc FAQ.html
  Log:
  tired tired tired of these stupid linux questions
  
  Revision  ChangesPath
  1.108 +35 -1 apache-1.3/htdocs/manual/misc/FAQ.html
  
  Index: FAQ.html
  ===
  RCS file: /export/home/cvs/apache-1.3/htdocs/manual/misc/FAQ.html,v
  retrieving revision 1.107
  retrieving revision 1.108
  diff -u -r1.107 -r1.108
  --- FAQ.html  1998/02/14 13:06:25 1.107
  +++ FAQ.html  1998/02/18 21:07:25 1.108
  @@ -15,7 +15,7 @@
 
 Apache Server Frequently Asked Questions
 
  -  $Revision: 1.107 $ ($Date: 1998/02/14 13:06:25 $)
  +  $Revision: 1.108 $ ($Date: 1998/02/18 21:07:25 $)
 
 
 The latest version of this FAQ is always available from the main
  @@ -265,6 +265,13 @@
   than 1.2.0 and suddenly I have problems with Apache dying randomly
   or not restarting properly
  
  +   I'm using RedHat Linux and my .htm files are 
showing
  +up as html source rather than being formatted!
  +   
  +   I'm using RedHat Linux 5.0, or some other glibc
  + based Linux system, and I get errors with the crypt 
function when
  + I attempt to build Apache 1.2.
  +
 

   
  @@ -2231,6 +2238,33 @@
   
   
 
  +
  +  I'm using RedHat Linux and my .htm files 
are showing
  +up as html source rather than being formatted!
  +
  +RedHat messed up and forgot to put a content type for 
.htm
  +files into /etc/mime.types.  Edit 
/etc/mime.types,
  +find the line containing html and add htm to 
it.
  +Then restart your httpd server:
  +
  + kill -HUP `cat /var/run/httpd.pid`
  +
  +Then clear your browsers' caches.  (Many browsers won't re-examine
  +the content type after they've reloaded a page.)
  +
  +
  +
  +  I'm using RedHat Linux 5.0, or some 
other glibc
  +based Linux system, and I get errors with the crypt 
function when
  +I attempt to build Apache 1.2.
  +
  +glibc puts the crypt function into a separate library.  Edit your
  +src/Configuration file and set this:
  +
  + EXTRA_LIBS=-lcrypt
  +
  +
  +

cvs commit: apache-1.3/htdocs/manual/misc FAQ.html

1998-02-14 Thread dgaudet 
dgaudet 98/02/14 05:06:26

  Modified:htdocs/manual/misc FAQ.html
  Log:
  I am tired tired tired of dealing with "kill -9" and "killall -whatever 
httpd" bugs
  
  Revision  ChangesPath
  1.107 +63 -1 apache-1.3/htdocs/manual/misc/FAQ.html
  
  Index: FAQ.html
  ===
  RCS file: /export/home/cvs/apache-1.3/htdocs/manual/misc/FAQ.html,v
  retrieving revision 1.106
  retrieving revision 1.107
  diff -u -r1.106 -r1.107
  --- FAQ.html  1998/02/11 15:14:33 1.106
  +++ FAQ.html  1998/02/14 13:06:25 1.107
  @@ -15,7 +15,7 @@
 
 Apache Server Frequently Asked Questions
 
  -  $Revision: 1.106 $ ($Date: 1998/02/11 15:14:33 $)
  +  $Revision: 1.107 $ ($Date: 1998/02/14 13:06:25 $)
 
 
 The latest version of this FAQ is always available from the main
  @@ -258,6 +258,13 @@
  I upgraded to Apache 1.3b and now my
   virtual hosts don't work!
  
  +   I'm using RedHat Linux and I have problems with 
httpd
  +dying randomly or not restarting properly
  +   
  +   I upgraded from an Apache version earlier
  +than 1.2.0 and suddenly I have problems with Apache dying randomly
  +or not restarting properly
  +   
 

   
  @@ -2169,6 +2176,61 @@
 
 

  +
  + I'm using RedHat Linux and I have problems 
with httpd
  +dying randomly or not restarting properly
  +
  +RedHat Linux versions 4.x (and possibly earlier) rpms contain
  +various nasty scripts which do not stop or restart Apache properly.
  +These can affect you even if you're not running the RedHat supplied
  +rpms.
  +
  + If you're using the default install then you're probably running
  +Apache 1.1.3, which is outdated.  From RedHat's ftp site you can
  +pick up a more recent RPM for Apache 1.2.x.  This will solve one of
  +the problems.
  +
  + If you're using a custom built Apache rather than the RedHat rpms
  +then you should rpm -e apache.  In particular you want
  +the mildly broken /etc/logrotate.d/apache script to be
  +removed, and you want the broken /etc/rc.d/init.d/httpd
  +(or httpd.init) script to be removed.  The latter is
  +actually fixed by the apache-1.2.5 rpms but if you're building your
  +own Apache then you probably don't want the RedHat files.
  +
  +We can't stress enough how important it is for folks, especially
  +vendors to follow the stopping Apache
  +directions given in our documentation.  In RedHat's defense,
  +the broken scripts were necessary with Apache 1.1.x because the
  +Linux support in 1.1.x was very poor, and there were various race
  +conditions on all platforms.  None of this should be necessary with
  +Apache 1.2 and later.
  +
  +
  +  
  +
  +  I upgraded from an Apache version earlier
  +than 1.2.0 and suddenly I have problems with Apache dying randomly
  +or not restarting properly
  +
  +You should read the previous note about
  +problems with RedHat installations.  It is entirely likely that your
  +installation has start/stop/restart scripts which were built for
  +an earlier version of Apache.  Versions earlier than 1.2.0 had
  +various race conditions that made it necessary to use
  +kill -9 at times to take out all the httpd servers.
  +But that should not be necessary any longer.  You should follow
  +the directions on how to stop
  +and restart Apache.
  +
  +As of Apache 1.3 there is a script
  +src/support/apachectl which, after a bit of
  +customization, is suitable for starting, stopping, and restarting
  +your server.
  +
  +
  +
  +

cvs commit: apache-1.3/htdocs/manual/misc FAQ.html compat_notes.html known_bugs.html security_tips.html

1998-02-11 Thread coar 
coar98/02/11 07:14:37

  Modified:htdocs/manual/misc FAQ.html compat_notes.html
known_bugs.html security_tips.html
  Log:
Clean up some references to "bugdb.cgi".
  
  Revision  ChangesPath
  1.106 +4 -4  apache-1.3/htdocs/manual/misc/FAQ.html
  
  Index: FAQ.html
  ===
  RCS file: /export/home/cvs/apache-1.3/htdocs/manual/misc/FAQ.html,v
  retrieving revision 1.105
  retrieving revision 1.106
  diff -u -r1.105 -r1.106
  --- FAQ.html  1998/02/05 09:58:38 1.105
  +++ FAQ.html  1998/02/11 15:14:33 1.106
  @@ -15,7 +15,7 @@
 
 Apache Server Frequently Asked Questions
 
  -  $Revision: 1.105 $ ($Date: 1998/02/05 09:58:38 $)
  +  $Revision: 1.106 $ ($Date: 1998/02/11 15:14:33 $)
 
 
 The latest version of this FAQ is always available from the main
  @@ -482,7 +482,7 @@
   Most problems that get reported to The Apache Group are recorded in
   the
   http://www.apache.org/bugdb.cgi";
  + HREF="http://bugs.apache.org/";
   >bug database.
   Please check the existing reports, open
   and closed, before adding one.  If you find
  @@ -516,7 +516,7 @@
   have obtained no relief, then please do let The Apache
   Group know about the problem by
   http://www.apache.org/bugdb.cgi";
  + HREF="http://www.apache.org/bug_report.html";
   >logging a bug report.
   
   
  @@ -1564,7 +1564,7 @@
 issues is the cause of your problem, and it hasn't been reported
 before, please submit a
 http://www.apache.org/bugdb.cgi";
  +   HREF="http://www.apache.org/bug_report.html";
 >problem report.
 Be sure to include complete details, such as the compiler
 & OS versions and exact error messages.
  
  
  
  1.19  +1 -1  apache-1.3/htdocs/manual/misc/compat_notes.html
  
  Index: compat_notes.html
  ===
  RCS file: /export/home/cvs/apache-1.3/htdocs/manual/misc/compat_notes.html,v
  retrieving revision 1.18
  retrieving revision 1.19
  diff -u -r1.18 -r1.19
  --- compat_notes.html 1998/01/26 16:53:49 1.18
  +++ compat_notes.html 1998/02/11 15:14:34 1.19
  @@ -22,7 +22,7 @@
   scratch, so certain liberties the earlier servers took may not be
   available here.  These are all easily fixable.  If you know of other
   non-fatal problems that belong here, http://www.apache.org/bugdb.cgi";>let us know.
  +HREF="http://www.apache.org/bug_report.html";>let us know.
   
   Please also check the known bugs
   page, and the known client
  
  
  
  1.43  +11 -11apache-1.3/htdocs/manual/misc/known_bugs.html
  
  Index: known_bugs.html
  ===
  RCS file: /export/home/cvs/apache-1.3/htdocs/manual/misc/known_bugs.html,v
  retrieving revision 1.42
  retrieving revision 1.43
  diff -u -r1.42 -r1.43
  --- known_bugs.html   1998/02/09 18:32:33 1.42
  +++ known_bugs.html   1998/02/11 15:14:35 1.43
  @@ -16,7 +16,7 @@
   Known Bugs in Apache
   
   The most up-to-date resource for bug tracking and information is the
  -http://www.apache.org/bugdb.cgi";>Apache bug database.
  +http://bugs.apache.org/index";>Apache bug database.
   Significant bugs at release time will also be noted there.
   If you are running a 1.2 beta release or version 1.1.3 or earlier
   and think you have found a bug, please upgrade to 1.2. Many bugs
  @@ -119,7 +119,7 @@
   USE_x_SERIALIZED_ACCEPT definitions, see the
   source file conf.h for your architecture.
   This is being tracked as
  -http://www.apache.org/bugdb.cgi/full/467";>PR#467.
  +http://bugs.apache.org/index/full/467";>PR#467.
   To resolve this problem, we are adding one of the above settings
   to the default settings for platforms as we discover which is 
   appropriate for them.  New as of 1.3b3: the server will
  @@ -131,7 +131,7 @@
   
   The PATH_INFO part of a request URI cannot include the sequence
   %2f. This will be tracked as
  -http://www.apache.org/bugdb.cgi/full/543";>PR#543.
  +http://bugs.apache.org/index/full/543";>PR#543.
   
   
   Users of early 1.2 betas reported problems with many
  @@ -154,14 +154,14 @@
   Compiling on Solaris 2 with SunSoft's C compiler gives the warning
   "mod_include.c", line 1123: warning: end-of-loop code not
   reached. This is a bogus warning and can be ignored.
  -See http://www.apache.org/bugdb.cgi/full/681";>PR#681.
  +See http://bugs.apache.org/index/full/681";>PR#681.
   
   
   If compilation fails complaining about "unknown symbol __inet_ntoa()"
   then you have probably installed version 8 of bind. You will need to
   explicitly link with the bind library by adding -lbind
   to EXTRA_LDFLAGS in Configuration. See
  -http://www.apache.org/bugdb.cgi/full/616";>PR#616
  +http: