diff options
| -rw-r--r-- | docs/manual/misc/FAQ.html | 57 |
1 files changed, 42 insertions, 15 deletions
diff --git a/docs/manual/misc/FAQ.html b/docs/manual/misc/FAQ.html index 850a33b4fc..0cfe9c2f7c 100644 --- a/docs/manual/misc/FAQ.html +++ b/docs/manual/misc/FAQ.html @@ -14,7 +14,7 @@ <!--#include virtual="header.html" --> <H1 ALIGN="CENTER">Apache Server Frequently Asked Questions</H1> <P> - $Revision: 1.125 $ ($Date: 1998/08/05 18:04:50 $) + $Revision: 1.126 $ ($Date: 1998/08/06 20:46:12 $) </P> <P> The latest version of this FAQ is always available from the main @@ -290,6 +290,9 @@ </LI> <LI><A HREF="#htaccess-work">My <CODE>.htaccess</CODE> files are being ignored.</A> + </LI> + <LI><A HREF="#submit_patch">How do I submit a patch to the Apache Group?</A> + </LI> </OL> </LI> </UL> @@ -412,7 +415,7 @@ occasional users. </LI> </UL> - </P> + <p></P> <HR> </LI> @@ -546,7 +549,7 @@ (dbx) where</CODE> </DD> </DL> - </P> + <p></P> <P> (Substitute the appropriate locations for your <SAMP>ServerRoot</SAMP> and your <SAMP>httpd</SAMP> and @@ -612,7 +615,7 @@ <DD><CODE>AddHandler cgi-script .cgi</CODE> </DD> </DL> - </P> + <p></P> <P> The server will then recognize that all files in that location (and its logical descendants) that end in "<SAMP>.cgi</SAMP>" @@ -624,7 +627,7 @@ declaration that includes the <SAMP>ExecCGI</SAMP> option. </LI> </OL> - </P> + <p></P> <P> In some situations, you might not want to actually allow all files named "<SAMP>*.cgi</SAMP>" to be executable. @@ -646,7 +649,7 @@ RewriteRule ^quux\.cgi$ - [T=application/x-httpd-cgi]</CODE> </DD> </DL> - </P> + <p></P> </LI> <LI>Make sure that the directory location is covered by an <A HREF="../mod/core.html#options"><SAMP>Options</SAMP></A> @@ -654,7 +657,7 @@ <SAMP>FollowSymLinks</SAMP> option. </LI> </OL> - </P> + <p></P> <HR> </LI> @@ -697,7 +700,7 @@ }</CODE> </DD> </DL> - </P> + <p></P> <P> 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 @@ <DD><CODE>AddHandler server-parsed .shtml</CODE> </DD> </DL> - </P> + <p></P> <P> 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</CODE> </DD> </DL> - </P> + <p></P> <P> More information about this issue can be found in the <A HREF="http://www.apache.org/info/jdk-102.html" @@ -1290,7 +1293,7 @@ This hurts performance and should only be used as a last resort. </LI> </UL> - </P> + <p></P> <HR> </LI> @@ -1363,7 +1366,7 @@ <DD><CODE>EXTRA_CFLAGS=-DMAXIMUM_DNS</CODE> </DD> </DL> - </P> + <p></P> <P> This will cause Apache to be very paranoid about making sure a particular host address is <EM>really</EM> assigned to the name it @@ -1441,7 +1444,7 @@ <DD><CODE>AddType audio/x-midi .mid .midi .kar</CODE> </DD> </DL> - </P> + <p></P> <P> Note that this may break browsers that <EM>do</EM> recognize the <SAMP>audio/midi</SAMP> MIME type unless they're prepared to also @@ -1582,7 +1585,7 @@ EXTRA_LIBS=-lbind</CODE> </DD> </DL> - </P> + <p></P> <HR> </LI> @@ -1692,7 +1695,7 @@ satisfy any</CODE> </DD> </DL> - </P> + <p></P> <P> See the <A HREF="#user-authentication">user authentication</A> question and the <A HREF="../mod/mod_access.html">mod_access</A> @@ -2297,6 +2300,30 @@ <A HREF="../mod/core.html#directory">Directory</A> container. <HR> </LI> + <LI><A NAME="submit_patch"> + <STRONG>How do I submit a patch to the Apache Group?</STRONG></A> + <P> + 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 <A HREF="http://www.apache.org/bug_report.html">bug report page</A>. + Improvements, modifications and additions should follow these instructions. + <P> + In general, the first course of action is to be a member of the + <code>new-httpd@apache.org</code> mailing list. This indicates to the Group that + you are closely following the latest Apache developments. Your patch file should be + generated using either '<code>diff -c</code>' or '<code>diff -u</code>' against the + latest CVS tree. To submit your patch, send Email to <code>new-httpd@apache.org</code> + with a <code>Subject:</code> line that starts with <code>[PATCH]</code> 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. + <P> + 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. + <HR> + </LI> <!-- Don't forget to add HR tags at the end of each list item.. --> |