From: Joshua Slive To find which directives can be placed in To find which directives can be placed in This document explains some of the directives provided by
+ This document explains some of the directives provided by the
core server which are used to configure
the basic operations of the server.Configuring Apache
+Configuration Files
-t
command line option.
functionality is included in the core server. Extended features are
available through modules which
can be loaded into Apache. By default, a base set of modules is
+HREF="mod/module-dict.html#Status">base set of modules is
included in the server at compile-time. If the server is compiled to
use dynamically loaded modules, then modules
can be compiled separately and added at any time using the .htaccess
files apply to the directory where you place
the file, and all sub-directories. The .htaccess
files
follow the same syntax as the main configuration files. Since
-.htaccess
files are read on every request, rather than
-only at server startup, changes made in these files take immediate
-effect.
+.htaccess
files are read on every request, changes made
+in these files take immediate effect.
.htaccess
files, check the Context
diff --git a/docs/manual/configuring.html.en b/docs/manual/configuring.html.en
index 26302c3df7..88d65eaae6 100644
--- a/docs/manual/configuring.html.en
+++ b/docs/manual/configuring.html.en
@@ -1,7 +1,7 @@
Configuring Apache
+Configuration Files
set of modules is
included in the server at compile-time. If the server is compiled to
use dynamically loaded modules, then modules
can be compiled separately and added at any time using the -t
command line option.
functionality is included in the core server. Extended features are
available through modules which
can be loaded into Apache. By default, a base set of modules is
+HREF="mod/module-dict.html#Status">base.htaccess
files apply to the directory where you place
the file, and all sub-directories. The .htaccess
files
follow the same syntax as the main configuration files. Since
-.htaccess
files are read on every request, rather than
-only at server startup, changes made in these files take immediate
-effect.
+.htaccess
files are read on every request, changes made
+in these files take immediate effect.
.htaccess
files, check the Context
diff --git a/docs/manual/server-wide.html b/docs/manual/server-wide.html
index 4636e49ab0..0adc2ab440 100644
--- a/docs/manual/server-wide.html
+++ b/docs/manual/server-wide.html
@@ -15,7 +15,7 @@
Server-Wide Configuration
-MaxClients
, while sites with limited memory may need to
decrease MaxClients
to keep the server from thrashing
-(swapping memory to disk and back).
While the parent process is usually started as root under Unix in order to bind to port 80, the child processes are launched @@ -197,7 +199,7 @@ configure how Apache handles persistent connections.
ThreadStackSizeThe Limit
* directives are used to place limits
+
The LimitRequest
* 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.
The ThreadStackSize
directive is used only
-on Netware to control the stock size.
This document explains some of the directives provided by +
This document explains some of the directives provided by the core server which are used to configure the basic operations of the server.
@@ -118,7 +118,9 @@ these directives from their default values. Sites which need to serve more than 256 simultaneous requests may need to increaseMaxClients
, while sites with limited memory may need to
decrease MaxClients
to keep the server from thrashing
-(swapping memory to disk and back).
+(swapping memory to disk and back). More information about tuning
+process creation is provided in the performance hints documentation.
While the parent process is usually started as root under Unix in order to bind to port 80, the child processes are launched @@ -197,7 +199,7 @@ configure how Apache handles persistent connections.
ThreadStackSizeThe Limit
* directives are used to place limits
+
The LimitRequest
* 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.
The ThreadStackSize
directive is used only
-on Netware to control the stock size.