mirror of
https://github.com/apache/httpd.git
synced 2025-10-30 08:05:39 +03:00
d140ffad9c
or it may give us a better starting point for 2.0 improvements. Fixed a bunch of <p>...</p> matches. Removed 1.3 upgrade recommendation. Fixed some entity encodings. Updated a bunch of links that moved from core.html to mpm_common.html. Fixed a few bad/stale links. Fixed a decrement that was interfering with comment. git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/trunk@88376 13f79535-47bb-0310-9956-ffa450edef68
272 lines
9.9 KiB
HTML
272 lines
9.9 KiB
HTML
<!--#if expr="$FAQMASTER" -->
|
|
<!--#set var="STANDALONE" value="" -->
|
|
<!--#set var="INCLUDED" value="YES" -->
|
|
<!--#if expr="$QUERY_STRING = TOC" -->
|
|
<!--#set var="TOC" value="YES" -->
|
|
<!--#set var="CONTENT" value="" -->
|
|
<!--#else -->
|
|
<!--#set var="TOC" value="" -->
|
|
<!--#set var="CONTENT" value="YES" -->
|
|
<!--#endif -->
|
|
<!--#else -->
|
|
<!--#set var="STANDALONE" value="YES" -->
|
|
<!--#set var="INCLUDED" value="" -->
|
|
<!--#set var="TOC" value="" -->
|
|
<!--#set var="CONTENT" value="" -->
|
|
<!--#endif -->
|
|
<!--#if expr="$STANDALONE" -->
|
|
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN">
|
|
<HTML>
|
|
<HEAD>
|
|
<TITLE>Apache Server Frequently Asked Questions</TITLE>
|
|
</HEAD>
|
|
<!-- Background white, links blue (unvisited), navy (visited), red (active) -->
|
|
<BODY
|
|
BGCOLOR="#FFFFFF"
|
|
TEXT="#000000"
|
|
LINK="#0000FF"
|
|
VLINK="#000080"
|
|
ALINK="#FF0000"
|
|
>
|
|
<!--#include virtual="header.html" -->
|
|
<H1 ALIGN="CENTER">Apache Server Frequently Asked Questions</H1>
|
|
<P>
|
|
$Revision: 1.9 $ ($Date: 2001/02/28 03:36:00 $)
|
|
</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"
|
|
REL="Help"
|
|
><SAMP>http://www.apache.org/docs/misc/FAQ.html</SAMP></A>>.
|
|
</P>
|
|
<!-- Notes about changes: -->
|
|
<!-- - If adding a relative link to another part of the -->
|
|
<!-- documentation, *do* include the ".html" portion. There's a -->
|
|
<!-- good chance that the user will be reading the documentation -->
|
|
<!-- on his own system, which may not be configured for -->
|
|
<!-- multiviews. -->
|
|
<!-- - When adding items, make sure they're put in the right place -->
|
|
<!-- - verify that the numbering matches up. -->
|
|
<!-- - *Don't* use <PRE></PRE> blocks - they don't appear -->
|
|
<!-- correctly in a reliable way when this is converted to text -->
|
|
<!-- with Lynx. Use <DL><DD><CODE>xxx<BR>xx</CODE></DD></DL> -->
|
|
<!-- blocks inside a <P></P> instead. This is necessary to get -->
|
|
<!-- the horizontal and vertical indenting right. -->
|
|
<!-- - Don't forget to include an HR tag after the last /P tag -->
|
|
<!-- but before the /LI in an item. -->
|
|
<P>
|
|
If you are reading a text-only version of this FAQ, you may find numbers
|
|
enclosed in brackets (such as "[12]"). These refer to the list of
|
|
reference URLs to be found at the end of the document. These references
|
|
do not appear, and are not needed, for the hypertext version.
|
|
</P>
|
|
<H2>The Questions</H2>
|
|
<OL TYPE="A">
|
|
<!--#endif -->
|
|
<!--#if expr="$TOC || $STANDALONE" -->
|
|
<LI VALUE="9"><STRONG>Features</STRONG>
|
|
<OL>
|
|
<LI><A HREF="#proxy">Does or will Apache act as a Proxy server?</A>
|
|
</LI>
|
|
<LI><A HREF="#multiviews">What are "multiviews"?</A>
|
|
</LI>
|
|
<LI><A HREF="#putsupport">Why can't I publish to my Apache server
|
|
using PUT on Netscape Gold and other programs?</A>
|
|
</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>
|
|
<LI><A HREF="#rotate">How can I rotate my log files?</A>
|
|
</LI>
|
|
<LI><A HREF="#conditional-logging">How do I keep certain requests from
|
|
appearing in my logs?</A>
|
|
</LI>
|
|
</OL>
|
|
</LI>
|
|
<!--#endif -->
|
|
<!--#if expr="$STANDALONE" -->
|
|
</OL>
|
|
|
|
<HR>
|
|
|
|
<H2>The Answers</H2>
|
|
<!--#endif -->
|
|
<!--#if expr="! $TOC" -->
|
|
|
|
<H3>I. Features</H3>
|
|
<OL>
|
|
|
|
<LI><A NAME="proxy">
|
|
<STRONG>Does or will Apache act as a Proxy server?</STRONG>
|
|
</A>
|
|
<P>
|
|
Apache version 1.1 and above comes with a
|
|
<A HREF="../mod/mod_proxy.html">proxy module</A>.
|
|
If compiled in, this will make Apache act as a caching-proxy server.
|
|
</P>
|
|
<HR>
|
|
</LI>
|
|
|
|
<LI><A NAME="multiviews">
|
|
<STRONG>What are "multiviews"?</STRONG>
|
|
</A>
|
|
<P>
|
|
"Multiviews" is the general name given to the Apache
|
|
server's ability to provide language-specific document variants in
|
|
response to a request. This is documented quite thoroughly in the
|
|
<A HREF="../content-negotiation.html" REL="Help">content negotiation</A>
|
|
description page. In addition, <CITE>Apache Week</CITE> carried an
|
|
article on this subject entitled
|
|
"<A HREF="http://www.apacheweek.com/features/negotiation" REL="Help"
|
|
><CITE>Content Negotiation Explained</CITE></A>".
|
|
</P>
|
|
<HR>
|
|
</LI>
|
|
|
|
<LI><A NAME="putsupport">
|
|
<STRONG>Why can't I publish to my Apache server using PUT on
|
|
Netscape Gold and other programs?</STRONG>
|
|
</A>
|
|
<P>
|
|
Because you need to install and configure a script to handle
|
|
the uploaded files. This script is often called a "PUT" handler.
|
|
There are several available, but they may have security problems.
|
|
Using FTP uploads may be easier and more secure, at least for now.
|
|
For more information, see the <CITE>Apache Week</CITE> article
|
|
<A HREF="http://www.apacheweek.com/features/put"
|
|
><CITE>Publishing Pages with PUT</CITE></A>.
|
|
</P>
|
|
<HR>
|
|
</LI>
|
|
|
|
<LI><A NAME="SSL-i">
|
|
<STRONG>Why doesn't Apache include SSL?</STRONG>
|
|
</A>
|
|
<P>
|
|
SSL (Secure Socket Layer) data transport requires encryption, and many
|
|
governments have restrictions upon the import, export, and use of
|
|
encryption technology. If Apache included SSL in the base package,
|
|
its distribution would involve all sorts of legal and bureaucratic
|
|
issues, and it would no longer be freely available. Also, some of
|
|
the technology required to talk to current clients using SSL is
|
|
patented by <A HREF="http://www.rsa.com/">RSA Data Security</A>,
|
|
who restricts its use without a license.
|
|
</P>
|
|
<P>
|
|
Some SSL implementations of Apache are available, however; see the
|
|
"<A HREF="http://www.apache.org/related_projects.html"
|
|
>related projects</A>"
|
|
page at the main Apache web site.
|
|
</P>
|
|
<P>
|
|
You can find out more about this topic in the <CITE>Apache Week</CITE>
|
|
article about
|
|
<A HREF="http://www.apacheweek.com/features/ssl" REL="Help"
|
|
><CITE>Apache and Secure Transactions</CITE></A>.
|
|
</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>), mod_layout, 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>
|
|
<LI><A NAME="rotate">
|
|
<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 <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/"
|
|
>http://www.ford-mason.co.uk/resources/cronolog/</A>. It can
|
|
automatically 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:</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">
|
|
<STRONG>How do I keep certain requests from appearing
|
|
in my logs?</STRONG></A>
|
|
<P>
|
|
The maximum flexibility for removing unwanted information from
|
|
log files is obtained by post-processing the logs, or using
|
|
piped-logs to feed the logs through a program which does whatever
|
|
you want. However, Apache does offer the ability to prevent
|
|
requests from ever appearing in the log files. You can do this by
|
|
using the
|
|
<A HREF="../mod/mod_setenvif.html#SetEnvIf"><CODE>SetEnvIf</CODE></A>
|
|
directive to set an environment variable for certain requests and
|
|
then using the conditional
|
|
<A HREF="../mod/mod_log_config.html#customlogconditional"><CODE>CustomLog</CODE></A>
|
|
syntax to prevent logging when the environment variable is set.
|
|
</P>
|
|
<HR>
|
|
</LI>
|
|
|
|
</OL>
|
|
<!--#endif -->
|
|
<!--#if expr="$STANDALONE" -->
|
|
<!-- Don't forget to add HR tags at the end of each list item.. -->
|
|
|
|
<!--#include virtual="footer.html" -->
|
|
</BODY>
|
|
</HTML>
|
|
<!--#endif -->
|