<module>mod_rewrite</module>
</modulelist>
<directivelist>
- <directive module="mod_authz_host">Allow</directive>
+ <directive module="mod_access_compat">Allow</directive>
<directive module="mod_log_config">CustomLog</directive>
- <directive module="mod_authz_host">Deny</directive>
+ <directive module="mod_access_compat">Deny</directive>
<directive module="mod_ext_filter">ExtFilterDefine</directive>
<directive module="mod_headers">Header</directive>
<directive module="mod_log_config">LogFormat</directive>
about missing modules.</p>
<p>In the following example, the <directive
-module="mod_mime_magic">MimeMagicFiles</directive> directive will be
+module="mod_mime_magic">MimeMagicFile</directive> directive will be
applied only if <module>mod_mime_magic</module> is available.</p>
<example>
<Location /foo/bar><br />
</Location>
</example>
-<p><directive type="section" module="core">Alias</directive>es on the other hand,
+<p><directive type="section" module="mod_alias">Alias</directive>es on the other hand,
are mapped vice-versa:</p>
<example>
Alias /foo/bar /srv/www/uncommon/bar<br />
<section id="nesting"><title>Nesting of sections</title>
<p>Some section types can be nested inside other section types. One the one
-hand, <directive type="section" module="core">File</directive> can be used
+hand, <directive type="section" module="core">Files</directive> can be used
inside <directive type="section" module="core">Directory</directive>. On
the other hand, <directive type="section" module="core">If</directive> can
be used inside <directive type="section" module="core">Directory</directive>,
Make sure that all parent directories (here <code>/opt</code>,
<code>/opt/apache</code> and <code>/opt/apache/logs</code>) have the x-bit
set for, at minimum, the UID under which Apache's children are running (see
- the <directive module="mpm_common">User</directive> directive).</p>
+ the <directive module="mod_unixd">User</directive> directive).</p>
</section>
<section id="entropy"><title>Why does mod_ssl stop with the error
<li>There are security partitioning issues, such as company1
does not want anyone at company2 to be able to read their
data except via the web. In this case you would need two
- daemons, each running with different <code class="directive"><a href="../mod/mpm_common.html#user">User</a></code>, <code class="directive"><a href="../mod/mpm_common.html#group">Group</a></code>, <code class="directive"><a href="../mod/mpm_common.html#listen">Listen</a></code>, and <code class="directive"><a href="../mod/core.html#serverroot">ServerRoot</a></code> settings.</li>
+ daemons, each running with different <code class="directive"><a href="../mod/mod_unixd.html#user">User</a></code>, <code class="directive"><a href="../mod/mod_unixd.html#group">Group</a></code>, <code class="directive"><a href="../mod/mpm_common.html#listen">Listen</a></code>, and <code class="directive"><a href="../mod/core.html#serverroot">ServerRoot</a></code> settings.</li>
<li>You can afford the memory and file descriptor
requirements of listening to every IP alias on the
does not want anyone at company2 to be able to read their
data except via the web. In this case you would need two
daemons, each running with different <directive
- module="mpm_common">User</directive>, <directive
- module="mpm_common">Group</directive>, <directive
+ module="mod_unixd">User</directive>, <directive
+ module="mod_unixd">Group</directive>, <directive
module="mpm_common">Listen</directive>, and <directive
module="core">ServerRoot</directive> settings.</li>