diff options
Diffstat (limited to 'usr.sbin/httpd/htdocs/manual/misc/FAQ.html')
| -rw-r--r-- | usr.sbin/httpd/htdocs/manual/misc/FAQ.html | 99 |
1 files changed, 56 insertions, 43 deletions
diff --git a/usr.sbin/httpd/htdocs/manual/misc/FAQ.html b/usr.sbin/httpd/htdocs/manual/misc/FAQ.html index b24bf19e14b..9d0cc579c40 100644 --- a/usr.sbin/httpd/htdocs/manual/misc/FAQ.html +++ b/usr.sbin/httpd/htdocs/manual/misc/FAQ.html @@ -21,15 +21,15 @@ <H1 ALIGN="CENTER">Apache Server Frequently Asked Questions</H1> <P> - $Revision: 1.7 $ ($Date: 2000/12/15 22:17:28 $) + $Revision: 1.8 $ ($Date: 2001/03/29 10:21:30 $) </P> <P> The latest version of this FAQ is always available from the main Apache web site, at <<A - HREF="http://www.apache.org/docs/misc/FAQ.html" + HREF="http://httpd.apache.org/docs/misc/FAQ.html" REL="Help" - ><SAMP>http://www.apache.org/docs/misc/FAQ.html</SAMP></A>>. + ><SAMP>http://httpd.apache.org/docs/misc/FAQ.html</SAMP></A>>. </P> <!-- Notes about changes: --> <!-- - If adding a relative link to another part of the --> @@ -237,7 +237,7 @@ fills with "<SAMP>fcntl: F_SETLKW: No record locks available</SAMP>" or similar messages</A> </LI> - <LI><A HREF="#aixccbug">Why am I getting "<SAMP>Expected </Directory> + <LI><A HREF="#aixccbug">Why am I getting "<SAMP>Expected </Directory> but saw </Directory></SAMP>" when I try to start Apache?</A> </LI> <LI><A HREF="#redhat">I'm using RedHat Linux and I have problems with httpd @@ -550,7 +550,8 @@ <LI><A NAME="what"> <STRONG>What is Apache?</STRONG> </A> - <P>The Apache httpd server + <p>The Apache httpd server</p> + <UL> <LI>is a powerful, flexible, HTTP/1.1 compliant web server <LI>implements the latest protocols, including HTTP/1.1 (RFC2616) @@ -603,7 +604,6 @@ </DL> </UL> - </P> <HR> </LI> @@ -611,7 +611,7 @@ <STRONG>How and why was Apache created?</STRONG> </A> <P> - The <A HREF="http://www.apache.org/ABOUT_APACHE.html">About Apache</A> + The <A HREF="http://httpd.apache.org/ABOUT_APACHE.html">About Apache</A> document explains how the Apache project evolved from its beginnings as an outgrowth of the NCSA httpd project to its current status as one of the fastest, most efficient, and most functional web servers @@ -714,7 +714,7 @@ There is no official support for Apache. None of the developers want to be swamped by a flood of trivial questions that can be resolved elsewhere. Bug reports and suggestions should be sent <EM>via</EM> - <A HREF="http://www.apache.org/bug_report.html">the bug report page</A>. + <A HREF="http://httpd.apache.org/bug_report.html">the bug report page</A>. Other questions should be directed to the <A HREF="news:comp.infosystems.www.servers.unix" >comp.infosystems.www.servers.unix</A> or <A HREF= @@ -737,12 +737,12 @@ </A> <P> Indeed there is. See the main - <A HREF="http://www.apache.org/httpd">Apache web site</A>. + <A HREF="http://httpd.apache.org/">Apache web site</A>. There is also a regular electronic publication called <A HREF="http://www.apacheweek.com/" REL="Help"><CITE>Apache Week</CITE></A> available. Links to relevant <CITE>Apache Week</CITE> articles are included below where appropriate. There are also some - <A HREF="http://www.apache.org/info/apache_books.html" + <A HREF="http://httpd.apache.org/info/apache_books.html" >Apache-specific books</A> available. </P> <HR> @@ -754,7 +754,7 @@ <P> You can find out how to download the source for Apache at the project's - <A HREF="http://www.apache.org/httpd">main web page</A>. + <A HREF="http://httpd.apache.org/">main web page</A>. </P> <HR> </LI> @@ -822,7 +822,7 @@ </P> </LI> <LI><STRONG>Check the - <A HREF="http://www.apache.org/docs/misc/FAQ.html">FAQ</A>!</STRONG> + <A HREF="http://httpd.apache.org/docs/misc/FAQ.html">FAQ</A>!</STRONG> <P> The latest version of the Apache Frequently-Asked Questions list can always be found at the main Apache web site. @@ -864,7 +864,7 @@ If you've gone through those steps above that are appropriate and have obtained no relief, then please <EM>do</EM> let The Apache Group know about the problem by - <A HREF="http://www.apache.org/bug_report.html">logging a bug report</A>. + <A HREF="http://httpd.apache.org/bug_report.html">logging a bug report</A>. </P> <P> If your problem involves the server crashing and generating a core @@ -984,7 +984,7 @@ 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 <A - HREF="http://www.apache.org/bug_report.html">bug report page</A>. + HREF="http://httpd.apache.org/bug_report.html">bug report page</A>. Improvements, modifications, and additions should follow the instructions below. </P> @@ -1063,8 +1063,7 @@ </A> <P> Check out Dean Gaudet's - <A HREF="http://www.apache.org/docs/misc/perf-tuning.html" - >performance tuning page</A>. + <A HREF="perf-tuning.html">performance tuning page</A>. </P> <HR> </LI> @@ -1075,17 +1074,17 @@ 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 + Regular expressions (aka "regex"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]/. + any "images" directory could be written as /\/images\/.*(jpg|gif)$/. </P> <P> 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 + We implement a simple subset of Perl's regex support, but it's still a good way to learn what they mean. You can start by going to the <A - HREF="http://www.perl.com/CPAN-local/doc/manual/html/pod/perlre.html#Version_8_Regular_Expresions" + HREF="http://www.perl.com/CPAN-local/doc/manual/html/pod/perlre.html#Regular_Expressions" >CPAN page on regular expressions</A>, and branching out from there. </P> @@ -1107,8 +1106,8 @@ <p> If you don't see a kit for your platform listed in the binary distribution area - (<URL:<a href="http://www.apache.org/dist/binaries/" - >http://www.apache.org/dist/binaries/</a>>), + (<URL:<a href="http://httpd.apache.org/dist/binaries/" + >http://httpd.apache.org/dist/binaries/</a>>), it means either that the platform isn't available to any of the developers, or that they just haven't gotten around to preparing a binary for it. As this is a voluntary project, @@ -1239,7 +1238,7 @@ platforms there are. If you have verified that none of the above issues is the cause of your problem, and it hasn't been reported before, please submit a - <A HREF="http://www.apache.org/bug_report.html">problem report</A>. + <A HREF="http://httpd.apache.org/bug_report.html">problem report</A>. Be sure to include <EM>complete</EM> details, such as the compiler & OS versions and exact error messages. </P> @@ -1421,9 +1420,9 @@ to rebuild the kernel with that support enabled (it's under the "General Setup" submenu). Documentation for kernel building is beyond the scope of this FAQ; you should consult the <A - HREF="http://www.linuxhq.com/HOWTO/Kernel-HOWTO.html" >Kernel + HREF="http://www.redhat.com/mirrors/LDP/HOWTO/Kernel-HOWTO.html">Kernel HOWTO</A>, or the documentation provided with your distribution, or - a <A HREF="http://www.linuxhq.com/HOWTO/META-FAQ.html" >Linux + a <A HREF="http://www.redhat.com/mirrors/LDP/HOWTO/META-FAQ.html">Linux newsgroup/mailing list</A>. As a last-resort workaround, you can comment out the <CODE>#define USE_SHMGET_SCOREBOARD</CODE> definition in the <SAMP>LINUX</SAMP> section of @@ -1471,7 +1470,7 @@ </LI> <LI><A NAME="aixccbug"><STRONG>Why am I getting "<SAMP>Expected - </Directory> but saw </Directory></SAMP>" when + </Directory> but saw </Directory></SAMP>" when I try to start Apache?</STRONG></A> <P> This is a known problem with certain versions of the AIX C compiler. @@ -1626,6 +1625,12 @@ >How to Add an Application to Aventail Connect's Application Exclusion List</a>." </p> + <p> + Apache is affected in a similar way by <em>any</em> firewall program that + isn't correctly configured. Assure you exclude your Apache server ports + (usually port 80) from the list of ports to block. Refer to your firewall + program's documentation for the how-to. + </p> <hr> </LI> <li><a name="err1067"><b>When I try to start Apache on Windows, I get @@ -1649,6 +1654,12 @@ The error you see will probably be one of those preceding this question in the FAQ. </p> + <p> + As of Apache 1.3.14, first check the Windows NT Event Log for + Application errors using the Windows NT/2000 Event Viewer program. + Any errors that occur prior to opening the Apache error log will + be stored here, if Apache is run as a Service on NT or 2000. As with + any error, also check your Apache error log. <hr> </li> </OL> @@ -1898,7 +1909,7 @@ <P></P> <P> More information about this issue can be found in the - <A HREF="http://www.apache.org/info/jdk-102.html" + <A HREF="http://httpd.apache.org/info/jdk-102.html" ><CITE>Java and HTTP/1.1</CITE></A> page at the Apache web site. </P> @@ -2038,7 +2049,7 @@ </P> <P> Apache 1.3b2 introduced a new directive, - <A HREF="http://www.apache.org/docs/mod/core.html#namevirtualhost" + <A HREF="../mod/core.html#namevirtualhost" ><SAMP>NameVirtualHost</SAMP></A>, which simplifies the rules quite a bit. However, changing the rules like this means that your existing name-based @@ -2229,7 +2240,7 @@ a line such as <P> <DL> - <DD><CODE>AddHandler cgi-script cgi</CODE> + <DD><CODE>AddHandler cgi-script .cgi</CODE> </DD> </DL> <P></P> @@ -2612,12 +2623,10 @@ Two alternatives are: <OL> <LI>Place the cgi-bin directory next to the public_html directory: - <P> <DL> <DD><CODE>ScriptAliasMatch ^/~([^/]*)/cgi-bin/(.*) /home/$1/cgi-bin/$2</CODE> </DD> </DL> - </P> </LI> <LI>Place the cgi-bin directory underneath the public_html directory: <P></p> @@ -2931,13 +2940,13 @@ </P> <P> To eliminate this problem you should + </P> <OL> <LI>Always use the trailing slash when requesting directories; <LI>Change the <CODE>ServerName</CODE> to match the name you are using in the URL; and/or <LI>Set <CODE>UseCanonicalName off</CODE>. </OL> - </P> <HR> </LI> @@ -3188,7 +3197,7 @@ </P> <P> Some SSL implementations of Apache are available, however; see the - "<A HREF="http://www.apache.org/related_projects.html" + "<A HREF="http://httpd.apache.org/related_projects.html" >related projects</A>" page at the main Apache web site. </P> @@ -3206,7 +3215,7 @@ </A> <P> You can make arbitrary changes to static documents by configuring an - <A HREF="http://www.apache.org/docs/mod/mod_actions.html#action"> + <A HREF="../mod/mod_actions.html#action"> Action</A> which launches a CGI script. The CGI is then responsible for setting a content-type and delivering the requested document (the location of which is passed in the @@ -3241,11 +3250,14 @@ <STRONG>How can I rotate my log files?</STRONG> </A> <P>The simple answer: by piping the transfer log into an appropriate - log file rotation utility.</P> - <P>The longer answer: In the src/support/ directory, you will find a - utility called <CODE>rotatelogs</CODE> which can be used like this:<PRE> - TransferLog "|/path/to/rotatelogs /path/to/logs/access_log 86400" - </PRE> to enable daily rotation of the log files.<BR> + log file rotation utility.</P> <P>The longer answer: In the + src/support/ directory, you will find a utility called <a + href="../programs/rotatelogs.html">rotatelogs</a> which can be used + like this:</p> + +<PRE> TransferLog "|/path/to/rotatelogs /path/to/logs/access_log 86400"</PRE> + + <p>to enable daily rotation of the log files.<BR> A more sophisticated solution of a logfile rotation utility is available under the name <CODE>cronolog</CODE> from Andrew Ford's site at <A HREF="http://www.ford-mason.co.uk/resources/cronolog/" @@ -3253,9 +3265,10 @@ create logfile subdirectories based on time and date, and can have a constant symlink point to the rotating logfiles. (As of version 1.6.1, cronolog is available under the <A HREF="../LICENSE">Apache License</A>). - Use it like this:<PRE> - CustomLog "|/path/to/cronolog --symlink=/usr/local/apache/logs/access_log /usr/local/apache/logs/%Y/%m/access_log" combined - </PRE></P> + Use it like this:</P> + +<PRE> CustomLog "|/path/to/cronolog --symlink=/usr/local/apache/logs/access_log /usr/local/apache/logs/%Y/%m/access_log" combined</PRE> + <HR> </LI> <LI><A NAME="conditional-logging"> @@ -3295,7 +3308,7 @@ The base Apache Web server package does not include ASP support. However, there are a couple of after-market solutions that let you add this functionality; see the - <a href="http://www.apache.org/related_projects.html" + <a href="http://httpd.apache.org/related_projects.html" >related projects</a> page to find out more. </p> <hr> |