<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN">
<HTML>
<HEAD>
-<TITLE>Configuring Apache</TITLE>
+<TITLE>Configuration Files</TITLE>
</HEAD>
<!-- Background white, links blue (unvisited), navy (visited), red (active) -->
ALINK="#FF0000"
>
<!--#include virtual="header.html" -->
-<H1 ALIGN="CENTER">Configuring Apache</H1>
+<H1 ALIGN="CENTER">Configuration Files</H1>
<ul>
<li><a href="#main">Main Configuration Files</a></li>
back-slash "\" may be used as the last character on a line to indicate
that the directive continues onto the next line. There must be no
other characters or white space between the back-slash and the end of
-the line. To end a line with a literal back-slash, you can escape it
-by preceding it with a second back-slash "\\".
+the line.
<P>Directives in the configuration files are case-insensitive, but
arguments to directives are often case sensitive. Lines which begin
functionality is included in the core server. Extended features are
available through <A HREF="mod/index-bytype.html">modules</A> which
can be loaded into Apache. By default, a <A
-HREF="mod/directive-dict.html#Status">base</A> set of modules is
+HREF="mod/module-dict.html#Status">base</A> set of modules is
included in the server at compile-time. If the server is compiled to
use <A HREF="dso.html">dynamically loaded</A> modules, then modules
can be compiled separately and added at any time using the <A
<CODE>.htaccess</CODE> files apply to the directory where you place
the file, and all sub-directories. The <CODE>.htaccess</CODE> files
follow the same syntax as the main configuration files. Since
-<CODE>.htaccess</CODE> files are read on every request, rather than
-only at server startup, changes made in these files take immediate
-effect.
+<CODE>.htaccess</CODE> files are read on every request, changes made
+in these files take immediate effect.
<P>To find which directives can be placed in <CODE>.htaccess</CODE>
files, check the <A HREF="mod/directive-dict.html#Context">Context</A>
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN">
<HTML>
<HEAD>
-<TITLE>Configuring Apache</TITLE>
+<TITLE>Configuration Files</TITLE>
</HEAD>
<!-- Background white, links blue (unvisited), navy (visited), red (active) -->
ALINK="#FF0000"
>
<!--#include virtual="header.html" -->
-<H1 ALIGN="CENTER">Configuring Apache</H1>
+<H1 ALIGN="CENTER">Configuration Files</H1>
<ul>
<li><a href="#main">Main Configuration Files</a></li>
back-slash "\" may be used as the last character on a line to indicate
that the directive continues onto the next line. There must be no
other characters or white space between the back-slash and the end of
-the line. To end a line with a literal back-slash, you can escape it
-by preceding it with a second back-slash "\\".
+the line.
<P>Directives in the configuration files are case-insensitive, but
arguments to directives are often case sensitive. Lines which begin
functionality is included in the core server. Extended features are
available through <A HREF="mod/index-bytype.html">modules</A> which
can be loaded into Apache. By default, a <A
-HREF="mod/directive-dict.html#Status">base</A> set of modules is
+HREF="mod/module-dict.html#Status">base</A> set of modules is
included in the server at compile-time. If the server is compiled to
use <A HREF="dso.html">dynamically loaded</A> modules, then modules
can be compiled separately and added at any time using the <A
<CODE>.htaccess</CODE> files apply to the directory where you place
the file, and all sub-directories. The <CODE>.htaccess</CODE> files
follow the same syntax as the main configuration files. Since
-<CODE>.htaccess</CODE> files are read on every request, rather than
-only at server startup, changes made in these files take immediate
-effect.
+<CODE>.htaccess</CODE> files are read on every request, changes made
+in these files take immediate effect.
<P>To find which directives can be placed in <CODE>.htaccess</CODE>
files, check the <A HREF="mod/directive-dict.html#Context">Context</A>
<!--#include virtual="header.html" -->
<h1 align="center">Server-Wide Configuration</h1>
-<p>This document explains some of the directives provided by
+<p>This document explains some of the directives provided by the
<a href="mod/core.html">core</A> server which are used to configure
the basic operations of the server.</p>
more than 256 simultaneous requests may need to increase
<code>MaxClients</code>, while sites with limited memory may need to
decrease <code>MaxClients</code> to keep the server from thrashing
-(swapping memory to disk and back).</p>
+(swapping memory to disk and back). More information about tuning
+process creation is provided in the <a
+href="misc/perf-tuning.html">performance hints</a> documentation.</p>
<p>While the parent process is usually started as root under Unix
in order to bind to port 80, the child processes are launched
<a href="mod/core.html#threadstacksize">ThreadStackSize</a><br>
</td></tr></table>
-<p>The <code>Limit</code>* directives are used to place limits
+<p>The <code>LimitRequest</code>* directives are used to place limits
on the amount of resources Apache will use in reading requests
from clients. By limiting these values, some kinds of denial
of service attacks can be mitigated.</p>
resources used by CGI scripts and SSI exec commands.</p>
<p>The <code>ThreadStackSize</code> directive is used only
-on Netware to control the stock size.</p>
+on Netware to control the stack size.</p>
<!--#include virtual="footer.html" -->
</BODY>
<!--#include virtual="header.html" -->
<h1 align="center">Server-Wide Configuration</h1>
-<p>This document explains some of the directives provided by
+<p>This document explains some of the directives provided by the
<a href="mod/core.html">core</A> server which are used to configure
the basic operations of the server.</p>
more than 256 simultaneous requests may need to increase
<code>MaxClients</code>, while sites with limited memory may need to
decrease <code>MaxClients</code> to keep the server from thrashing
-(swapping memory to disk and back).</p>
+(swapping memory to disk and back). More information about tuning
+process creation is provided in the <a
+href="misc/perf-tuning.html">performance hints</a> documentation.</p>
<p>While the parent process is usually started as root under Unix
in order to bind to port 80, the child processes are launched
<a href="mod/core.html#threadstacksize">ThreadStackSize</a><br>
</td></tr></table>
-<p>The <code>Limit</code>* directives are used to place limits
+<p>The <code>LimitRequest</code>* directives are used to place limits
on the amount of resources Apache will use in reading requests
from clients. By limiting these values, some kinds of denial
of service attacks can be mitigated.</p>
resources used by CGI scripts and SSI exec commands.</p>
<p>The <code>ThreadStackSize</code> directive is used only
-on Netware to control the stock size.</p>
+on Netware to control the stack size.</p>
<!--#include virtual="footer.html" -->
</BODY>
projects / apache / commitdiff