From firstname.lastname@example.org Thu Aug 06 20:46:21 1998
- $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 @@
Apache Server Frequently Asked Questions
.htaccess files are being
- $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 @@
(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] -+
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 -+
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 -+
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. +
+ 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 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
email@example.com 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
+ with a
Subject: line that starts with
+ 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 about your patches and possibly defend + your code. If your patch results in a lot of discussion, you may be asked to + submit an updated patch that incorporate all changes and suggestions.