it listens to all addresses on the machine. However, it may need to
be told to listen on specific ports, or only on selected
addresses, or a combination of both. This is often combined with the
- <a href="vhosts">Virtual Host</a> feature, which determines how
+ <a href="vhosts/">Virtual Host</a> feature, which determines how
<code>httpd</code> responds to different IP addresses, hostnames and
ports.</p>
<p>If you have to support a client which sends broken headers and
which can't be fixed, a simple workaround involving <module>mod_setenvif
- </module> and <module>mod_header</module> allows you to still accept
+ </module> and <module>mod_headers</module> allows you to still accept
these headers:</p>
<highlight language="config">
<module>mod_substitute</module>
<module>mod_xml2enc</module>
<module>mod_proxy_html</module>
- <module>mod_policy</module>
</modulelist>
<directivelist>
<directive module="mod_filter">FilterChain</directive>
other than who they are. Something such as where they are
coming from.</p>
- <p>The authorization providers <directive module="mod_authz_host">
- all</directive>, <directive module="mod_authz_host">
- env</directive>, <directive module="mod_authz_host">
- host</directive> and <directive module="mod_authz_host">
- ip</directive> let you allow or deny access based other host based
- criteria such as host name or ip address of the machine requesting
- a document.</p>
+ <p>The authorization providers <code>all</code>,
+ <code>env</code>, <code>host</code> and <code>ip</code> let you
+ allow or deny access based other host based criteria such as
+ host name or ip address of the machine requesting a
+ document.</p>
<p>The usage of these providers is specified through the
<directive module="mod_authz_core">Require</directive> directive.
<section id="moreinformation"><title>More information</title>
<p>You should also read the documentation for
- <module>mod_auth_basic</module> and <module>mod_authz_host</module> which
- contain some more information about how this all works.
- The directive <directive module="mod_authn_core"><AuthnProviderAlias></directive>
- can also help in simplifying certain authentication configurations.</p>
+ <module>mod_auth_basic</module> and <module>mod_authz_host</module>
+ which contain some more information about how this all works. The
+ directive <directive type="section"
+ module="mod_authn_core">AuthnProviderAlias</directive> can also help
+ in simplifying certain authentication configurations.</p>
<p>The various ciphers supported by Apache for authentication data are
explained in <a href="../misc/password_encryptions.html">Password
<directive module="core">Options</directive>
<directive module="mod_mime">AddHandler</directive>
<directive module="core">SetHandler</directive>
- <directive module="core">AuthType</directive>
- <directive module="core">AuthName</directive>
+ <directive module="mod_authn_core">AuthType</directive>
+ <directive module="mod_authn_core">AuthName</directive>
<directive module="mod_authn_file">AuthUserFile</directive>
<directive module="mod_authz_groupfile">AuthGroupFile</directive>
- <directive module="core">Require</directive>
+ <directive module="mod_authz_core">Require</directive>
</directivelist>
</related>
<p>From 2.4.8 onwards, named groups and backreferences are captured and
written to the environment with the corresponding name prefixed with
"MATCH_" and in upper case. This allows elements of paths to be referenced
- from within <a href="expr.html">expressions</a> and modules like
+ from within <a href="../expr.html">expressions</a> and modules like
<module>mod_rewrite</module>. In order to prevent confusion, numbered
(unnamed) backreferences are ignored. Use named groups instead.</p>
<p>From 2.4.8 onwards, named groups and backreferences are captured and
written to the environment with the corresponding name prefixed with
"MATCH_" and in upper case. This allows elements of files to be referenced
- from within <a href="expr.html">expressions</a> and modules like
+ from within <a href="../expr.html">expressions</a> and modules like
<module>mod_rewrite</module>. In order to prevent confusion, numbered
(unnamed) backreferences are ignored. Use named groups instead.</p>
documentation is available in <a href="../expr.html">Expressions in
Apache HTTP Server</a>.</p>
- <p>Only directives that support the <a href="mod/directive-dict.html#Context"
+ <p>Only directives that support the <a href="directive-dict.html#Context"
>directory context</a> can be used within this configuration section.</p>
</usage>
<p>From 2.4.8 onwards, named groups and backreferences are captured and
written to the environment with the corresponding name prefixed with
"MATCH_" and in upper case. This allows elements of URLs to be referenced
- from within <a href="expr.html">expressions</a> and modules like
+ from within <a href="../expr.html">expressions</a> and modules like
<module>mod_rewrite</module>. In order to prevent confusion, numbered
(unnamed) backreferences are ignored. Use named groups instead.</p>
contain at least the (set of) root URI(s) for this space.
Omitting to do so will cause the client to send the
Authorization header for <em>every request</em> sent to this
- server. Apart from increasing the size of the request, it may
- also have a detrimental effect on performance if <directive
- module="mod_auth_digest">AuthDigestNcCheck</directive> is on.</p>
+ server.</p>
<p>The URIs specified can also point to different servers, in
which case clients (which understand this) will then share
</note>
<p>The encrypted password format depends on which authentication
- frontend (e.g. <module>mod_authn_basic</module> or
- <module>mod_auth
n_digest</module>) is being used. See <a
+ frontend (e.g. <module>mod_auth_basic</module> or
+ <module>mod_auth_digest</module>) is being used. See <a
href="../misc/password_encryptions.html">Password Formats</a> for
more information.</p>
<p>When the <directive module="mod_cache">CacheHeader</directive> directive
is switched on, an <strong>X-Cache</strong> header will be added to the response
with the cache status of this response. If the normal handler is used, this
- directive may appear within a <directive module="core"><Directory></directive>
- or <directive module="core"><Location></directive> directive. If the quick
+ directive may appear within a <directive module="core" type="section">Directory</directive>
+ or <directive module="core" type="section">Location</directive> directive. If the quick
handler is used, this directive must appear within a server or virtual host
context, otherwise the setting will be ignored.</p>
used by the service and client.</p>
<p>If the normal handler is used, this directive may appear within a
- <directive module="core"><Directory></directive> or
- <directive module="core"><Location></directive> directive. If the quick handler
+ <directive module="core" type="section">Directory</directive> or
+ <directive module="core" type="section">Location</directive> directive. If the quick handler
is used, this directive must appear within a server or virtual host context, otherwise
the setting will be ignored.</p>
# run on output
SetOutputFilter gzip
- # mod_header directive to add
+ # mod_headers directive to add
# "Content-Encoding: gzip" header field
Header set Content-Encoding gzip
</Location>
<section id="order"><title>処理の順番</title>
- <p><module>mod_header</module> のディレクティブはサーバ設定のほぼどこにでも
+ <p><module>mod_headers</module> のディレクティブはサーバ設定のほぼどこにでも
書くことができ、影響する範囲を<a
href="../sections.html">設定用セクション</a>で囲むことで限定する
ことができます。</p>
<directive module="mod_so">LoadFile</directive>.</li>
<li>Directives which control the configuration file itself, such as
<directive module="core">Include</directive>,
- <directive module="core"><IfModule></directive> and
- <directive module="core"><IfDefine></directive> are not
+ <directive module="core" type="section">IfModule</directive> and
+ <directive module="core" type="section">IfDefine</directive> are not
listed, but the included configuration directives are.</li>
<li>Comments are not listed. (This may be considered a feature.)</li>
<li>Configuration directives from <code>.htaccess</code> files are
not listed (since they do not form part of the permanent server
configuration).</li>
<li>Container directives such as
- <directive module="core"><Directory></directive>
+ <directive module="core" type="section">Directory</directive>
are listed normally, but <module>mod_info</module> cannot figure
out the line number for the closing
- <directive module="core"></Directory></directive>.</li>
+ <directive module="core" type="section" name="Directory">/Directory</directive>.</li>
<li>Directives generated by third party modules such as <a href="http://perl.apache.org">mod_perl</a>
might not be listed.</li>
</ul>
<p>From 2.5.0 onwards, named groups and backreferences are captured and
written to the environment with the corresponding name prefixed with
"MATCH_" and in upper case. This allows elements of URLs to be referenced
- from within <a href="expr.html">expressions</a> and modules like
+ from within <a href="../expr.html">expressions</a> and modules like
<module>mod_rewrite</module>. In order to prevent confusion, numbered
(unnamed) backreferences are ignored. Use named groups instead.</p>
<p>Once replaced as instructed, this overridden useragent IP address is
then used for the <module>mod_authz_host</module>
- <directive module="mod_authz_host" type="section">Require ip</directive>
+ <directive module="mod_authz_core" name="require">Require ip</directive>
feature, is reported by <module>mod_status</module>, and is recorded by
<module>mod_log_config</module> <code>%a</code> and <module>core</module>
<code>%a</code> format strings. The underlying client IP of the connection
</highlight>
</example>
- <p>The <var>NSS</var> crypto driver might have already been configured by another
- part of the server, for example from <module>mod_nss</module> or
- <module>mod_ldap</module>. If found to have already been configured,
- a warning will be logged, and the existing configuration will have taken affect.
- To avoid this warning, use the noinit parameter as follows.</p>
+ <p>The <var>NSS</var> crypto driver might have already been
+ configured by another part of the server, for example from
+ <code>mod_nss</code> or <module>mod_ldap</module>. If found to
+ have already been configured, a warning will be logged, and the
+ existing configuration will have taken affect. To avoid this
+ warning, use the noinit parameter as follows.</p>
<example><title>NSS with certificate database</title>
<highlight language="config">
<seealso><a href="../bind.html">Setting which addresses and ports Apache
uses</a></seealso>
-<directivesynopsis location="mpm_common"><name>User</name>
+<directivesynopsis location="mod_unixd"><name>User</name>
</directivesynopsis>
-<directivesynopsis location="mpm_common"><name>Group</name>
+<directivesynopsis location="mod_unixd"><name>Group</name>
</directivesynopsis>
<directivesynopsis location="mpm_common"><name>Listen</name>
</directivesynopsis>
browsers to request that content be compressed before delivery,
saving network bandwidth.</dd>
- <dt><module>mod_auth_ldap</module></dt>
+ <dt><module outdated="true">mod_auth_ldap</module></dt>
<dd>New module in Apache httpd 2.0.41. This module allows an LDAP
database to be used to store credentials for HTTP Basic
using <module>mod_include</module>'s variables <code>$0</code>
.. <code>$9</code>.</dd>
- <dt><module>mod_auth_dbm</module></dt>
+ <dt><module outdated="true">mod_auth_dbm</module></dt>
<dd>Now supports multiple types of DBM-like databases using the
- <a href="../2.0/mod/mod_auth_dbm.html#AuthDBMType"><code>AuthDBMType</code></a>
- directive.</dd>
+ <directive>AuthDBMType</directive> directive.</dd>
</dl>
</section>
</tr>
<tr>
- <td><module>mod_access</module></td>
+ <td><module outdated="true">mod_access</module></td>
<td class="centered">+</td>
<td></td>
</tr>
</tr>
<tr>
- <td><module>mod_auth</module></td>
+ <td><module outdated="true">mod_auth</module></td>
<td class="centered">+</td>
<td></td>
</tr>
</tr>
<tr>
- <td><module>mod_log_referer</module></td>
+ <td><module outdated="true">mod_log_referer</module></td>
<td class="centered">+</td>
<td></td>
</tr>
<a href="http://httpd.apache.org/bug_report.html">bug reporting
page.</a></p>
- <p>The bug reporting page and dev-httpd mailing list are <em>not</em>
- provided to answer questions about configuration or running Apache.
- Before you submit a bug report or request, first consult this document, the
- <a href="../faq/">Frequently Asked Questions</a> page and the other
- relevant documentation topics. If you still have a question or problem,
- post it to the <a href="news://developer-forums.novell.com/novell.devsup.webserver">
- novell.devsup.webserver</a> newsgroup, where many Apache users are more than
- willing to answer new and obscure questions about using Apache on NetWare.</p>
+ <p>The bug reporting page and dev-httpd mailing list are
+ <em>not</em> provided to answer questions about configuration or
+ running Apache. Before you submit a bug report or request, first
+ consult this document, the <a
+ href="http://wiki.apache.org/httpd/FAQ">Frequently Asked
+ Questions</a> page and the other relevant documentation topics. If
+ you still have a question or problem, post it to the <a
+ href="news://developer-forums.novell.com/novell.devsup.webserver">
+ novell.devsup.webserver</a> newsgroup, where many Apache users are
+ more than willing to answer new and obscure questions about using
+ Apache on NetWare.</p>
<p>Most of this document assumes that you are installing Apache
from a binary distribution. If you want to compile Apache
<p>Apache is configured by reading configuration files usually stored
in the <code>conf</code> directory. These are the same as files used
to configure the Unix version, but there are a few different directives for
- Apache on NetWare. See the <a href="../">Apache
+ Apache on NetWare. See the <a href="../mod/">Apache module
documentation</a> for all the available directives.</p>
<p>The main differences in Apache for NetWare are:</p>
<p>To find out which modules are compiled by default, run
<code>./configure -h</code> or <code>./configure --help</code>
and look under <code>Optional Features</code>. Suppose you
- are interested in <module>mod_example1</module> and
- <module>mod_example2</module>, and you
+ are interested in <code>mod_example1</code> and
+ <code>mod_example2</code>, and you
see this:</p>
<example><pre>Optional Features:
limitations under the License.
-->
-<manualpage metafile="other.xml.meta">
+<manualpage metafile="log_server_status.xml.meta">
<parentdocument href="./">Programs</parentdocument>
<title>log_server_status - Log periodic status summaries</title>
limitations under the License.
-->
-<manualpage metafile="other.xml.meta">
+<manualpage metafile="split-logfile.xml.meta">
<parentdocument href="./">Programs</parentdocument>
<title>split-logfile - Split up multi-vhost logfiles</title>
limitations under the License.
-->
-<manualpage metafile="avoid.xml.meta">
+<manualpage metafile="advanced.xml.meta">
<parentdocument href="./">Rewrite</parentdocument>
<title>Advanced Techniques with mod_rewrite</title>
limitations under the License.
-->
-<manualpage metafile="avoid.xml.meta">
+<manualpage metafile="advanced.xml.meta">
<parentdocument href="./">Rewrite</parentdocument>
<title>Advanced Techniques with mod_rewrite</title>
<page href="server-wide.html">Server-Wide Configuration</page>
<page href="logs.html">Log Files</page>
<page href="urlmapping.html">Mapping URLs to Filesystem Locations</page>
-<page href="misc/security_tips.html">Security Tips</page>
<page href="dso.html">Dynamic Shared Object (DSO) support</page>
+<page href="compliance.html">HTTP Protocol Compliance</page>
<page href="content-negotiation.html">Content Negotiation</page>
<page href="custom-error.html">Custom error responses</page>
<page href="bind.html">Setting which addresses and ports Apache uses</page>
<page href="filter.html">Filters</page>
<page href="socache.html">Shared Object Cache Support</page>
<page href="suexec.html">suEXEC Support</page>
-<page href="misc/perf-tuning.html">Performance Hints</page>
+<page href="dns-caveats.html">Issues Regarding DNS and Apache</page>
<page href="http://wiki.apache.org/httpd/FAQ">Frequently Asked Questions</page>
</category>
<page href="vhosts/examples.html">VirtualHost Examples</page>
<page href="vhosts/details.html">An In-Depth Discussion of Virtual Host Matching</page>
<page href="vhosts/fd-limits.html">File descriptor limitations</page>
-<page href="dns-caveats.html">Issues Regarding DNS and Apache</page>
</category>
<category id="rewrite">
<page separate="yes" href="rewrite/">Overview</page>
<page href="mod/mod_rewrite.html">mod_rewrite reference
documentation</page>
-<page href="rewrite/intro.html">Introduction</page>
-<page href="rewrite/flags.html">Flags</page>
-<page href="rewrite/tech.html">Technical details</page>
-<page href="rewrite/remapping.html">Remapping URLs</page>
-<page href="rewrite/access.html">Access control</page>
+<page href="rewrite/intro.html">Introduction to regular expressions and
+mod_rewrite</page>
+<page href="rewrite/remapping.html">Using mod_rewrite for redirection and
+remapping of URLs</page>
+<page href="rewrite/access.html">Using mod_rewrite to control access</page>
+<page href="rewrite/vhosts.html">Dynamic virtual hosts with mod_rewrite</page>
+<page href="rewrite/proxy.html">Dynamic proxying with mod_rewrite</page>
+<page href="rewrite/rewritemap.html">Using RewriteMap</page>
<page href="rewrite/advanced.html">Advanced techniques</page>
+<page href="rewrite/avoid.html">When NOT to use mod_rewrite</page>
+<page href="rewrite/flags.html">RewriteRule Flags</page>
+<page href="rewrite/tech.html">Technical details</page>
</category>
<category id="ssl">
<category id="howto">
<title>Guides, Tutorials, and HowTos</title>
<page separate="yes" href="howto/">Overview</page>
-<page href="howto/auth.html">Authentication</page>
+<page href="howto/auth.html">Authentication and Authorization</page>
+<page href="howto/access.html">Access Control</page>
<page href="howto/cgi.html">Dynamic Content with CGI</page>
<page href="howto/ssi.html">Introduction to Server Side Includes</page>
<page href="howto/htaccess.html">.htaccess files</page>
Windows</page>
<page href="platform/win_compiling.html">Compiling Apache for
Microsoft Windows</page>
+<page href="platform/rpm.html">Using Apache With RPM Based Systems</page>
<page href="platform/netware.html">Using Apache with Novell NetWare</page>
<page href="platform/perf-hp.html">Running a High-Performance Web
Server on HPUX</page>
<page href="programs/apxs.html">Manual Page: apxs</page>
<page href="programs/configure.html">Manual Page: configure</page>
<page href="programs/dbmmanage.html">Manual Page: dbmmanage</page>
+<page href="programs/fcgistarter.html">Manual Page: fcgistarter</page>
+<page href="programs/firehose.html">Manual Page: firehose</page>
<page href="programs/htcacheclean.html">Manual Page: htcacheclean</page>
<page href="programs/htdbm.html">Manual Page: htdbm</page>
<page href="programs/htdigest.html">Manual Page: htdigest</page>
<page href="programs/htpasswd.html">Manual Page: htpasswd</page>
+<page href="programs/httxt2dbm.html">Manual Page: httxt2dbm</page>
<page href="programs/logresolve.html">Manual Page: logresolve</page>
+<page href="programs/log_server_status.html">Manual Page:
+log_server_status</page>
<page href="programs/rotatelogs.html">Manual Page: rotatelogs</page>
+<page href="programs/split-logfile.html">Manual Page: split-logfile</page>
<page href="programs/suexec.html">Manual Page: suexec</page>
<page href="programs/other.html">Other Programs</page>
</category>
<category id="misc">
<title>Apache Miscellaneous Documentation</title>
<page separate="yes" href="misc/">Overview</page>
+<page href="misc/perf-tuning.html">Performance Notes - Apache Tuning</page>
+<page href="misc/perf-scaling.html">Performance Scaling</page>
+<page href="misc/security_tips.html">Security Tips</page>
<page href="misc/relevant_standards.html">Relevant Standards</page>
+<page href="misc/password_encryptions.html">Password Encryption Formats</page>
</category>
<category id="modules">
<page separate="yes" href="developer/">Overview</page>
<page href="developer/API.html">Apache API notes</page>
<page href="developer/new_api_2_4.html">API updates in Apache HTTPD 2.4</page>
-<page href="developer/debugging.html">Debugging Memory Allocation in APR</page>
-<page href="developer/documenting.html">Documenting Apache 2.x</page>
+<page href="developer/modguide.html">Developing modules for Apache HTTPD 2.4</page>
+<page href="developer/documenting.html">Documenting Apache HTTPD</page>
<page href="developer/hooks.html">Apache 2.x Hook Functions</page>
-<page href="developer/modules.html">Converting Modules from Apache 1.3 to Apache 2.x</page>
-<page href="developer/request.html">Request Processing in Apache 2.x</page>
-<page href="developer/filters.html">How Filters Work in Apache 2.x</page>
+<page href="developer/modules.html">Converting Modules from 1.3 to 2.x</page>
+<page href="developer/request.html">Request Processing in 2.x</page>
+<page href="developer/filters.html">How Filters Work in 2.x</page>
+<page href="developer/output-filters.html">Guidelines for output filters in 2.x</page>
+<page href="developer/thread_safety.html">Thread Safety Issues in 2.x</page>
</category>
<category id="index">
command. Alternatively, you can append the following standard 1024-bit DH
parameters from <a href="http://www.ietf.org/rfc/rfc2409.txt">RFC 2409</a>,
section 6.2 to the respective
- <directive module="ssl">SSLCertificateFile</directive> file:</p>
+ <directive module="mod_ssl">SSLCertificateFile</directive> file:</p>
<example><pre>-----BEGIN DH PARAMETERS-----
MIGHAoGBAP//////////yQ/aoiFowjTExmKLgNwc0SkCTgiKZ8x0Agu+pjsTmyJR
Sgh5jjQE3e+VGbPNOkMbMCsKbfJfFDdP4TVtbVHCReSFtXZiXn7G9ExC6aY37WsL
<directive module="mod_alias">Alias</directive>
<directive module="mod_alias">AliasMatch</directive>
<directive module="mod_speling">CheckSpelling</directive>
-<directive module="core">DirectoryIndex</directive>
+<directive module="mod_dir">DirectoryIndex</directive>
<directive module="core">DocumentRoot</directive>
<directive module="core">ErrorDocument</directive>
<directive module="core">Options</directive>
<p>If a directory is requested (i.e. a path ending with
<code>/</code>), the file served from that directory is defined by
- the <directive module="core">DirectoryIndex</directive> directive.
+ the <directive module="mod_dir">DirectoryIndex</directive> directive.
For example, if <code>DocumentRoot</code> were set as above, and
you were to set:</p>
virtual host through to a server running on another machine. In the
example, a virtual host of the same name is configured on a machine
at <code>192.168.111.2</code>. The <directive
- module="mod_proxy">ProxyPreserveHost On</directive> directive is
- used so that the desired hostname is passed through, in case we are
- proxying multiple hostnames to a single machine.</p>
+ module="mod_proxy" name="ProxyPreserveHost">ProxyPreserveHost
+ On</directive> directive is used so that the desired hostname is
+ passed through, in case we are proxying multiple hostnames to a
+ single machine.</p>
<highlight language="config">
<VirtualHost *:*>
<p>This will create a log file in the common log format, but with the
canonical virtual host (whatever appears in the
<directive module="core">ServerName</directive> directive) prepended to
-each line. (See <directive
-module="mod_log_config">Custom Log Formats</directive> for
+each line. (See <module>mod_log_config</module> for
more about customizing your log files.)</p>
<p>When you wish to split your log file into its component parts (one
projects / apache / commitdiff