</dl>
<p>As a degenerate case, a <em>SubNet</em> with 32 valid bits is the
- equivalent to an <var><a href="#ipadr">IPAddr</a></var>, while a <var>SubNet</var> with zero
+ equivalent to an <var><a href="#ipaddr">IPAddr</a></var>, while a <var>SubNet</var> with zero
valid bits (<em>e.g.</em>, 0.0.0.0/0) is the same as the constant
<var>_Default_</var>, matching any IP address.</p></dd>
event that you have an enormous number of virtual hosts, consider using
<module>mod_vhost_alias</module> to create these hosts automatically.</p>
-<p>Third-party modules such as <a href="link_needed">mod_macro</a> are
+<p>Third-party modules such as <a href="http://people.apache.org/~fabien/mod_macro/">mod_macro</a> are
also useful for creating a large number of virtual hosts dynamically.</p>
<p>Using <module>mod_rewrite</module> for vitualhost creation may be
<p>Consider using either <directive
module="mod_proxy">ProxyPass</directive> or <directive
- module="mod_rewrite">ProxyPassMatch</directive> whenever possible in
+ module="mod_proxy">ProxyPassMatch</directive> whenever possible in
preference to mod_rewrite.</p>
</dd>
</dl>
<Directory> block or in a .htaccess file), so that the
<code>-f</code> checks are looking at the correct directory path.
You may need to set a <directive
- module="mod_rewite">RewriteBase</directive> directive to specify the
+ module="mod_rewrite">RewriteBase</directive> directive to specify the
directory base that you're working in.</p>
</dd>
</dl>
<dd>
<p>The very best way to solve this doesn't involve mod_rewrite at all,
-but rather uses the <directive module="alias">Redirect</directive>
+but rather uses the <directive module="mod_alias">Redirect</directive>
directive placed in a virtual host for the non-canonical
hostname(s).</p>
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>
conditions with some configurations.</p>
<p>Care has been taken to ensure that on-disk files
- such as the <directive module="core">Lockfile</directive> and <directive
+ such as the <directive module="mpm_common">Lockfile</directive> and <directive
module="mod_cgid">ScriptSock</directive> files contain the server
PID, and should coexist without problem. However, if a configuration
directive, third-party module or persistent CGI utilises any other on-disk
<directive module="core">KeepAliveTimeout</directive>,
<directive module="core">KeepAlive</directive>,
<directive module="core">MaxKeepAliveRequests</directive>,
- <directive module="core">ReceiveBufferSize</directive>,
- or <directive module="core">SendBufferSize</directive>
+ <directive module="mpm_common">ReceiveBufferSize</directive>,
+ or <directive module="mpm_common">SendBufferSize</directive>
directive then the respective value is inherited from the
main_server. (That is, inherited from whatever the final
setting of that value is in the main_server.)</li>