You are viewing a plain text version of this content. The canonical link for it is here.
Posted to cvs@httpd.apache.org by rb...@apache.org on 2026/04/14 20:08:29 UTC
svn commit: r1933072 - httpd/httpd/branches/2.4.x/docs/manual/rewrite
Author: rbowen
Date: Tue Apr 14 20:08:29 2026
New Revision: 1933072
Log:
Apply diffs from trunk. (Formatting, style guide)
Modified:
httpd/httpd/branches/2.4.x/docs/manual/rewrite/avoid.xml
httpd/httpd/branches/2.4.x/docs/manual/rewrite/remapping.xml
httpd/httpd/branches/2.4.x/docs/manual/rewrite/tech.xml
httpd/httpd/branches/2.4.x/docs/manual/rewrite/vhosts.xml
Modified: httpd/httpd/branches/2.4.x/docs/manual/rewrite/avoid.xml
==============================================================================
--- httpd/httpd/branches/2.4.x/docs/manual/rewrite/avoid.xml Tue Apr 14 20:06:32 2026 (r1933071)
+++ httpd/httpd/branches/2.4.x/docs/manual/rewrite/avoid.xml Tue Apr 14 20:08:29 2026 (r1933072)
@@ -156,7 +156,7 @@ server.</p>
<section id="vhosts"><title>Virtual Hosting</title>
<p>Although it is possible to handle <a href="vhosts.html">virtual hosts
-with <module>mod_rewrite</module></a>, it is seldom the right way. Creating individual
+with mod_rewrite</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
Modified: httpd/httpd/branches/2.4.x/docs/manual/rewrite/remapping.xml
==============================================================================
--- httpd/httpd/branches/2.4.x/docs/manual/rewrite/remapping.xml Tue Apr 14 20:06:32 2026 (r1933071)
+++ httpd/httpd/branches/2.4.x/docs/manual/rewrite/remapping.xml Tue Apr 14 20:08:29 2026 (r1933072)
@@ -30,7 +30,7 @@
<p>This document supplements the <module>mod_rewrite</module>
<a href="../mod/mod_rewrite.html">reference documentation</a>. It describes
how you can use <module>mod_rewrite</module> to redirect and remap
-request. This includes many examples of common uses of mod_rewrite,
+request. 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
@@ -113,7 +113,7 @@ RewriteRule "^<strong>/foo</strong>\.
<dd>
<p>In this example, as contrasted to the <a
href="#old-to-new-intern">internal</a> example above, we can simply
- use the Redirect directive. mod_rewrite was used in that earlier
+ use the Redirect directive. <module>mod_rewrite</module> was used in that earlier
example in order to hide the redirect from the client:</p>
<highlight language="config">
@@ -238,9 +238,9 @@ RewriteRule "^foo\.html$" "foo.cgi"
<dt>Discussion</dt>
<dd>
- <p>This example uses an often-overlooked feature of mod_rewrite,
+ <p>This example uses an often-overlooked feature of <module>mod_rewrite</module>,
by taking advantage of the order of execution of the ruleset. In
- particular, mod_rewrite evaluates the left-hand-side of the
+ particular, <module>mod_rewrite</module> evaluates the left-hand-side of the
RewriteRule before it evaluates the RewriteCond directives.
Consequently, $1 is already defined by the time the RewriteCond
directives are evaluated. This allows us to test for the existence
@@ -276,7 +276,7 @@ RewriteRule "^foo\.html$" "foo.cgi"
<dd>
-<p>The very best way to solve this doesn't involve mod_rewrite at all,
+<p>The very best way to solve this doesn't involve <module>mod_rewrite</module> at all,
but rather uses the <directive module="mod_alias">Redirect</directive>
directive placed in a virtual host for the non-canonical
hostname(s).</p>
@@ -313,7 +313,7 @@ might do the following:</p>
</If>
</highlight>
-<p>If, for whatever reason, you still want to use <code>mod_rewrite</code>
+<p>If, for whatever reason, you still want to use <module>mod_rewrite</module>
- if, for example, you need this to work with a larger set of RewriteRules -
you might use one of the recipes below.</p>
Modified: httpd/httpd/branches/2.4.x/docs/manual/rewrite/tech.xml
==============================================================================
--- httpd/httpd/branches/2.4.x/docs/manual/rewrite/tech.xml Tue Apr 14 20:06:32 2026 (r1933071)
+++ httpd/httpd/branches/2.4.x/docs/manual/rewrite/tech.xml Tue Apr 14 20:08:29 2026 (r1933072)
@@ -26,7 +26,7 @@
<title>Apache mod_rewrite Technical Details</title>
<summary>
-<p>This document discusses some of the technical details of mod_rewrite
+<p>This document discusses some of the technical details of <module>mod_rewrite</module>
and URL matching.</p>
</summary>
<seealso><a href="../mod/mod_rewrite.html">Module documentation</a></seealso>
@@ -47,7 +47,7 @@ and URL matching.</p>
like URL-to-filename translation, authentication, authorization,
content, and logging. (This is not an exhaustive list.)</p>
- <p>mod_rewrite acts in two of these phases (or "hooks", as they are
+ <p><module>mod_rewrite</module> acts in two of these phases (or "hooks", as they are
often called) to influence how URLs may be rewritten.</p>
<p>First, it uses the URL-to-filename translation hook, which occurs
@@ -59,7 +59,7 @@ and URL matching.</p>
<p>So, after a request comes in and a corresponding server or
virtual host has been determined, the rewriting engine starts
- processing any <code>mod_rewrite</code> directives appearing in the
+ processing any <module>mod_rewrite</module> directives appearing in the
per-server configuration. (i.e., in the main server configuration file
and <directive module="core" type="section">Virtualhost</directive>
sections.) This happens in the URL-to-filename phase.</p>
@@ -70,13 +70,13 @@ and URL matching.</p>
type="section">Directory</directive> blocks) are applied. This
happens in the Fixup phase.</p>
- <p>In each of these cases, mod_rewrite rewrites the
+ <p>In each of these cases, <module>mod_rewrite</module> rewrites the
<code>REQUEST_URI</code> either to a new URL, or to a filename.</p>
<p>In per-directory context (i.e., within <code>.htaccess</code> files
and <code>Directory</code> blocks), these rules are being applied
after a URL has already been translated to a filename. Because of
- this, the URL-path that mod_rewrite initially compares <directive
+ this, the URL-path that <module>mod_rewrite</module> initially compares <directive
module="mod_rewrite">RewriteRule</directive> directives against
is the full filesystem path to the translated filename with the current
directories path (including a trailing slash) removed from the front.</p>
@@ -127,7 +127,7 @@ and URL matching.</p>
</table>
- <p>For even more insight into how mod_rewrite manipulates URLs in
+ <p>For even more insight into how <module>mod_rewrite</module> manipulates URLs in
different contexts, you should consult the <a
href="../mod/mod_rewrite.html#logging">log entries</a> made during
rewriting.</p>
@@ -136,7 +136,7 @@ and URL matching.</p>
<section id="InternalRuleset"><title>Ruleset Processing</title>
- <p>Now when mod_rewrite is triggered in these two API phases, it
+ <p>Now when <module>mod_rewrite</module> is triggered in these two API phases, it
reads the configured rulesets from its configuration
structure (which itself was either created on startup for
per-server context or during the directory walk of the Apache
@@ -163,9 +163,9 @@ and URL matching.</p>
<dfn>Figure 1:</dfn>The control flow through the rewriting ruleset
</p>
<p>First the URL is matched against the
- <em>Pattern</em> of each rule. If it fails, mod_rewrite
+ <em>Pattern</em> of each rule. If it fails, <module>mod_rewrite</module>
immediately stops processing this rule, and continues with the
- next rule. If the <em>Pattern</em> matches, mod_rewrite looks
+ next rule. If the <em>Pattern</em> matches, <module>mod_rewrite</module> looks
for corresponding rule conditions (RewriteCond directives,
appearing immediately above the RewriteRule in the configuration).
If none are present, it substitutes the URL with a new value, which is
Modified: httpd/httpd/branches/2.4.x/docs/manual/rewrite/vhosts.xml
==============================================================================
--- httpd/httpd/branches/2.4.x/docs/manual/rewrite/vhosts.xml Tue Apr 14 20:06:32 2026 (r1933071)
+++ httpd/httpd/branches/2.4.x/docs/manual/rewrite/vhosts.xml Tue Apr 14 20:08:29 2026 (r1933072)
@@ -32,7 +32,7 @@
how you can use <module>mod_rewrite</module> to create dynamically
configured virtual hosts.</p>
-<note type="warning">mod_rewrite is not the best way to configure
+<note type="warning"><module>mod_rewrite</module> is not the best way to configure
virtual hosts. You should first consider the <a
href="../vhosts/mass.html">alternatives</a> before resorting to
mod_rewrite. See also the "<a href="avoid.html#vhosts">how to avoid
@@ -101,7 +101,7 @@ captured into the backreferences <code>$
etc.</p>
<p>
-As with many techniques discussed in this document, mod_rewrite really
+As with many techniques discussed in this document, <module>mod_rewrite</module> really
isn't the best way to accomplish this task. You should, instead,
consider using <module>mod_vhost_alias</module> instead, as it will much
more gracefully handle anything beyond serving static files, such as any
@@ -119,15 +119,15 @@ dynamic content, and Alias resolution.
thing as <a href="#per-hostname">the first example</a>. The first
half is very similar to the corresponding part above, except for
some changes, required for backward compatibility and to make the
- <code>mod_rewrite</code> part work properly; the second half
- configures <code>mod_rewrite</code> to do the actual work.</p>
+ <module>mod_rewrite</module> part work properly; the second half
+ configures <module>mod_rewrite</module> to do the actual work.</p>
- <p>Because <code>mod_rewrite</code> runs before other URI translation
- modules (e.g., <code>mod_alias</code>), <code>mod_rewrite</code> must
+ <p>Because <module>mod_rewrite</module> runs before other URI translation
+ modules (e.g., <module>mod_alias</module>), <module>mod_rewrite</module> must
be told to explicitly ignore any URLs that would have been handled
by those modules. And, because these rules would otherwise bypass
any <code>ScriptAlias</code> directives, we must have
- <code>mod_rewrite</code> explicitly enact those mappings.</p>
+ <module>mod_rewrite</module> explicitly enact those mappings.</p>
<highlight language="config">
# get the server name from the Host: header