<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">
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>
</summary>
<seealso><directive module="core">SetHandler</directive></seealso>
-<seealso><directive module="mime">AddHandler</directive></seealso>
+<seealso><directive module="mod_mime">AddHandler</directive></seealso>
<directivesynopsis>
<name>AllowHandlers</name>
</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 type="section" module="core">Directory</directive>
+ or <directive type="section" module="core">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 type="section" module="core">Directory</directive> or
+ <directive type="section" module="core">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 type="section" module="core">IfModule</directive> and
+ <directive type="section" module="core">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 type="section" module="core">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 type="section" module="core" 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>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">
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
<directive>AuthDBMType</directive> directive.</dd>
certain authentication configurations.
</dd>
- <dt><module>mod_authnz_ldap</module></dt>
+ <dt><module outdated="true">mod_authnz_ldap</module></dt>
<dd>This module is a port of the 2.0
<code>mod_auth_ldap</code> module to the 2.2 <code>Authn/Authz</code>
framework. New features include using LDAP attribute values and
<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:
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