<!--#include virtual="header.html" -->
<H1 ALIGN="CENTER">Apache Server Frequently Asked Questions</H1>
<P>
- $Revision: 1.1 $ ($Date: 1999/06/24 15:02:51 $)
+ $Revision: 1.2 $ ($Date: 1999/07/03 22:12:49 $)
</P>
<P>
The latest version of this FAQ is always available from the main
<STRONG>How thoroughly tested is Apache?</STRONG>
</A>
<P>
- Apache is run on over 1.2 million Internet servers (as of July 1998). It has
+ Apache is run on over 3 million Internet servers (as of June 1999). 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 half of all
<!--#include virtual="header.html" -->
<H1 ALIGN="CENTER">Apache Server Frequently Asked Questions</H1>
<P>
- $Revision: 1.1 $ ($Date: 1999/06/24 15:02:52 $)
+ $Revision: 1.2 $ ($Date: 1999/07/03 22:12:49 $)
</P>
<P>
The latest version of this FAQ is always available from the main
<LI><A HREF="#htaccess-work">My <CODE>.htaccess</CODE> files are being
ignored.</A>
</LI>
+ <LI><A HREF="#forbidden">Why do I get a
+ "<SAMP>Forbidden</SAMP>" message whenever I try to
+ access a particular directory?</A>
</OL>
</LI>
<!--#endif -->
</P>
<HR>
</LI>
+ <LI><A NAME="forbidden">
+ <STRONG>Why do I get a "<SAMP>Forbidden</SAMP>" message
+ whenever I try to access a particular directory?</A>
+ <P>
+ This message is generally caused because either
+ <UL>
+ <LI>The underlying file system permissions do not allow the
+ User/Group under which Apache is running to access the necessary
+ files; or
+ <LI>The Apache configuration has some access restrictions in
+ place which forbid access to the files.
+ </UL>
+ You can determine which case applies to your situation by checking the
+ error log.
+ </P>
+ <P>
+ In the case where file system permission are at fault, remember
+ that not only must the directory and files in question be readable,
+ but also all parent directories must be at least searchable by the
+ web server in order for the content to be accessible.
+ </P>
+ <HR>
+ </LI>
</OL>
<!--#endif -->
<!--#if expr="$STANDALONE" -->
<!--#include virtual="header.html" -->
<H1 ALIGN="CENTER">Apache Server Frequently Asked Questions</H1>
<P>
- $Revision: 1.1 $ ($Date: 1999/06/24 15:02:52 $)
+ $Revision: 1.2 $ ($Date: 1999/07/03 22:12:50 $)
</P>
<P>
The latest version of this FAQ is always available from the main
server. To see if this is the case, try running the script standalone
from an interactive session, rather than as a script under the server.
If you get error messages, this is almost certainly the cause of the
- "premature end of script headers" message.
+ "premature end of script headers" message. Even if the CGI
+ runs fine from the command line, remember that the environment and
+ permissions may be different when running under the web server. The
+ CGI can only access resources allowed for the <A
+ HREF="../mod/core.html#user"><CODE>User</CODE></A> and
+ <A HREF="../mod/core.html#group"><CODE>Group</CODE></A> specified in
+ your Apache configuration. In addition, the environment will not be
+ the same as the one provided on the command line, but it can be
+ adjusted using the directives provided by <A
+ HREF="../mod/mod_env.html">mod_env</A>.
</P>
<P>
The second most common cause of this (aside from people not
get the message if the CGI script was killed due to a
resource limit.
</P>
+ <P>
+ In addition, a configuration problem in <A
+ HREF="../suexec.html">suEXEC</A>, mod_perl, or another third party
+ module can often interfere with the execution of your CGI and cause
+ the "premature end of script headers" message.
+ </P>
<HR>
</LI>
<!--#include virtual="header.html" -->
<H1 ALIGN="CENTER">Apache Server Frequently Asked Questions</H1>
<P>
- $Revision: 1.2 $ ($Date: 1999/06/24 15:06:27 $)
+ $Revision: 1.3 $ ($Date: 1999/07/03 22:12:50 $)
</P>
<P>
The latest version of this FAQ is always available from the main
</LI>
<LI><A HREF="#SSL-i">Why doesn't Apache include SSL?</A>
</LI>
+ <LI><A HREF="#footer">How can I attach a footer to my documents
+ without using SSI?</A>
+ </LI>
+ <LI><A HREF="#search">Does Apache include a search engine?</A>
+ </LI>
</OL>
</LI>
<!--#endif -->
</P>
<HR>
</LI>
+ <LI><A NAME="footer">
+ <STRONG>How can I attach a footer to my documents
+ without using SSI?</STRONG>
+ </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">
+ 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
+ <SAMP>PATH_TRANSLATED</SAMP> environment variable), along with
+ whatever footer is needed.
+ </P>
+ <P>
+ Busy sites may not want to run a CGI script on every request, and
+ should consider using an Apache module to add the footer. There are
+ several third party modules available through the <A
+ HREF="http://modules.apache.org/">Apache Module Registry</A> which
+ will add footers to documents. These include mod_trailer, PHP
+ (<SAMP>php3_auto_append_file</SAMP>), and mod_perl
+ (<SAMP>Apache::Sandwich</SAMP>).
+ </P>
+ <HR>
+ </LI>
+ <LI><A NAME="search">
+ <STRONG>Does Apache include a search engine?</STRONG>
+ </A>
+ <P>Apache does not include a search engine, but there are many good
+ commercial and free search engines which can be used easily with
+ Apache. Some of them are listed on the <A
+ HREF="http://www.searchtools.com/tools/tools.html">Web Site Search
+ Tools</A> page. Open source search engines that are often used with
+ Apache include <A HREF="http://www.htdig.org/">ht://Dig</A> and <A
+ HREF="http://sunsite.berkeley.edu/SWISH-E/">SWISH-E</A>.
+ </P>
+ <HR>
+ </LI>
</OL>
<!--#endif -->
<!--#if expr="$STANDALONE" -->
projects / apache / commitdiff