0N/A<!
DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN">
0N/A <
TITLE>Definitions of terms used to describe Apache modules
180N/A<!-- Background white, links blue (unvisited), navy (visited), red (active) --> 0N/A <
H1 ALIGN="CENTER">Terms Used to Describe Apache Modules</
H1>
0N/A Each Apache module is described using a common format that looks
5N/A ><
STRONG>Status:</
STRONG></
A> <
EM>status</
EM>
0N/A ><
STRONG>Source File:</
STRONG></
A> <
EM>source-file</
EM>
0N/A HREF="#ModuleIdentifier" 0N/A ><
STRONG>Module Identifier:</
STRONG></
A> <
EM>module-identifier</
EM>
27N/A HREF="#Compatibility" 27N/A ><
STRONG>Compatibility:</
STRONG></
A> <
EM>compatibility notes</
EM>
0N/A Each of the attributes, complete with values where possible, are
0N/A described in this document.
0N/A <
H2>Module Terms</
H2>
0N/A <
LI><
A HREF="#Status">Status</
A>
0N/A <
LI><
A HREF="#SourceFile">Source File</
A>
27N/A <
LI><
A HREF="#ModuleIdentifier">Module Identifier</
A>
27N/A <
LI><
A HREF="#Compatibility">Compatibility</
A>
27N/A <
H2><
A NAME="Status">Status</
A></
H2>
32N/A This indicates how tightly bound into the Apache Web server the
32N/A module is; in other words, you may need to recompile the server in
315N/A order to gain access to the module and its functionality. Possible
315N/A values for this attribute are:
27N/A <
DT><
STRONG>MPM</
STRONG>
27N/A <
DD>A module with status "MPM" is a <
a 27N/A href="/mpm.html">Multi-Processing Module</
a>. Unlike the other
27N/A types of modules, Apache must have one and only one MPM in use at
27N/A any time. This type of module is responsible for basic request
27N/A handling and dispatching.
27N/A <
DT><
STRONG>Base</
STRONG>
27N/A <
DD>A module labeled as having "Base" status is compiled
311N/A and loaded into the server by default, and is therefore normally
27N/A available unless you have taken steps to remove the module from your
27N/A <
DT><
STRONG>Extension</
STRONG>
311N/A <
DD>A module with "Extension" status is not normally
311N/A compiled and loaded into the server. To enable the module and its
311N/A functionality, you may need to change the server build
311N/A configuration files and re-compile Apache.
311N/A <
DT><
STRONG>Experimental</
STRONG>
189N/A <
DD>"Experimental" status indicates that the module is
27N/A available as part of the Apache kit, but you are on your own if you
27N/A try to use it. The module is being documented for completeness,
27N/A and is not necessarily supported.
27N/A <
DT><
STRONG>External</
STRONG>
27N/A <
DD>Modules which are not included with the base Apache
27N/A distribution ("third-party modules") may use the
27N/A "External" status. We are not responsible for, nor do we
27N/A support such modules.
27N/A <
H2><
A NAME="SourceFile">Source File</
A></
H2>
27N/A This quite simply lists the name of the source file which contains
27N/A the code for the module. This is also the name used by the <
A 27N/A <
H2><
A NAME="ModuleIdentifier">Module Identifier</
A></
H2>
27N/A This is a string which identifies the module for use in the <
A 27N/A dynamically loading modules. In particular, it is the name
27N/A of the external variable of type module in the source file.
27N/A <
H2><
A NAME="Compatibility">Compatibility</
A></
H2>
27N/A If the module was not part of the original Apache version 2
27N/A distribution, the version in which it was introduced should be listed