mpm_common—A set of 20 directives common to all MPM modules
prefork—A nonthreaded, preforking web server that works much like
to earlier (1.3) versions of Apache
worker—A hybrid multiprocess multithreaded server
MPM enables Apache to be used on equipment with fewer resources yet still
handle massive numbers of hits and provide stable service. The worker
module provides directives to control how many simultaneous connections
your server can handle.
NOTE
Other MPMs related to other platforms are available for Apache, such as
mpm_netware for NetWare hosts and mpm_winnt for NT platforms. An
MPM named perchild, which provides user ID assignment to selected
daemon processes, is under development. For more information, browse to
the Apache Software Foundation’s home page, at www.apache.org.
Using .htaccess Configuration Files
Apache supports special configuration files, known as .htaccess files.
Almost any directive that appears in apache2.conf can appear in an
.htaccess file. This file, specified in the AccessFileName directive in
apache2.conf, sets configurations on a per-directory (usually in a user
directory) basis. As the system administrator, you can specify both the name
of this file and which of the server configurations can be overridden by the
contents of this file. This is especially useful for sites in which there are
multiple content providers and you want to control what these people can do
with their space.
To limit which server configurations the .htaccess files can override, use
the AllowOverride directive. AllowOverride can be set globally or
per directory. For example, in your apache2.conf file, you could use the
following:
Click here to view code image
Each directory to which Apache has access can be configured with
respect