<a href="../mod/mod_rewrite.html">reference documentation</a>. It describes
how you can use <module>mod_rewrite</module> to control access to
various resources, and other related techniques.
-This includes many examples of common uses of mod_rewrite,
+This includes many examples of common uses of <module>mod_rewrite</module>,
including detailed descriptions of how each works.</p>
<note type="warning">Note that many of these examples won't work unchanged in your
<dd>
<p>If all you wish to do is deny access to the resource, rather
than redirecting that request elsewhere, this can be
- accomplished without the use of mod_rewrite:</p>
+ accomplished without the use of <module>mod_rewrite</module>:</p>
<highlight language="config">
SetEnvIf Referer example\.com localreferer
</p>
<p>Note that there are methods of accomplishing this which do
- not use mod_rewrite. Note also that any technique that relies on
+ not use <module>mod_rewrite</module>. Note also that any technique that relies on
the clients <code>USER_AGENT</code> string can be circumvented
very easily, since that string can be changed.</p>
</dd>
<dd>
<p>
- Rather than using mod_rewrite for this, you can accomplish the
+ Rather than using <module>mod_rewrite</module> for this, you can accomplish the
same end using alternate means, as illustrated here:
</p>
<highlight language="config">
<section id="vhosts"><title>Virtual Hosting</title>
<p>Although it is possible to handle <a href="vhosts.html">virtual hosts
-with mod_rewrite</a>, it is seldom the right way. Creating individual
+with <module>mod_rewrite</module></a>, it is seldom the right way. Creating individual
<directive module="core" type="section">VirtualHost</directive> blocks is
almost always the right way to go. In the
event that you have an enormous number of virtual hosts, consider using
passthrough, depending on what <a href="flags.html">flags</a> you
attach to the rules.</p>
- <p>Since mod_rewrite is so powerful, it can indeed be rather
+ <p>Since <module>mod_rewrite</module> is so powerful, it can indeed be rather
complex. This document supplements the <a
href="../mod/mod_rewrite.html">reference documentation</a>, and
attempts to allay some of that complexity, and provide highly
annotated examples of common scenarios that you may handle with
- mod_rewrite. But we also attempt to show you when you should not
- use mod_rewrite, and use other standard Apache features instead,
+ <module>mod_rewrite</module>. But we also attempt to show you when you should not
+ use <module>mod_rewrite</module>, and use other standard Apache features instead,
thus avoiding this unnecessary complexity.</p>
projects / thirdparty / apache / httpd.git / commitdiff
