You are viewing a plain text version of this content. The canonical link for it is here.
Posted to cvs@httpd.apache.org by nd...@apache.org on 2006/02/06 19:09:05 UTC
svn commit: r375324 [2/4] - /httpd/httpd/branches/2.0.x/docs/manual/mod/
Modified: httpd/httpd/branches/2.0.x/docs/manual/mod/mod_rewrite.html.en
URL: http://svn.apache.org/viewcvs/httpd/httpd/branches/2.0.x/docs/manual/mod/mod_rewrite.html.en?rev=375324&r1=375323&r2=375324&view=diff
==============================================================================
--- httpd/httpd/branches/2.0.x/docs/manual/mod/mod_rewrite.html.en (original)
+++ httpd/httpd/branches/2.0.x/docs/manual/mod/mod_rewrite.html.en Mon Feb 6 10:09:02 2006
@@ -31,64 +31,27 @@
<tr><th><a href="module-dict.html#Compatibility">Compatibility:</a></th><td>Available in Apache 1.3 and later</td></tr></table>
<h3>Summary</h3>
- <blockquote>
- <p>``The great thing about mod_rewrite is it gives you
- all the configurability and flexibility of Sendmail.
- The downside to mod_rewrite is that it gives you all
- the configurability and flexibility of Sendmail.''</p>
-
- <p class="cite">-- <cite>Brian Behlendorf</cite><br />
- Apache Group</p>
-
- </blockquote>
-
- <blockquote>
- <p>`` Despite the tons of examples and docs,
- mod_rewrite is voodoo. Damned cool voodoo, but still
- voodoo. ''</p>
-
- <p class="cite">-- <cite>Brian Moore</cite><br />
- bem@news.cmc.net</p>
-
- </blockquote>
-
-
- <p>Welcome to mod_rewrite, the Swiss Army Knife of URL
- manipulation!</p>
-
<p>This module uses a rule-based rewriting engine (based on a
regular-expression parser) to rewrite requested URLs on the
fly. It supports an unlimited number of rules and an
- unlimited number of attached rule conditions for each rule to
+ unlimited number of attached rule conditions for each rule, to
provide a really flexible and powerful URL manipulation
mechanism. The URL manipulations can depend on various tests,
- for instance server variables, environment variables, HTTP
- headers, time stamps and even external database lookups in
- various formats can be used to achieve a really granular URL
+ of server variables, environment variables, HTTP
+ headers, or time stamps. Even external database lookups in
+ various formats can be used to achieve highly granular URL
matching.</p>
<p>This module operates on the full URLs (including the
path-info part) both in per-server context
(<code>httpd.conf</code>) and per-directory context
- (<code>.htaccess</code>) and can even generate query-string
+ (<code>.htaccess</code>) and can generate query-string
parts on result. The rewritten result can lead to internal
sub-processing, external request redirection or even to an
internal proxy throughput.</p>
- <p>But all this functionality and flexibility has its
- drawback: complexity. So don't expect to understand this
- entire module in just one day.</p>
-
- <p>This module was invented and originally written in April
- 1996 and gifted exclusively to the The Apache Group in July 1997
- by</p>
-
- <p class="indent">
- <a href="http://www.engelschall.com/"><code>Ralf S.
- Engelschall</code></a><br />
- <a href="mailto:rse@engelschall.com"><code>rse@engelschall.com</code></a><br />
- <a href="http://www.engelschall.com/"><code>www.engelschall.com</code></a>
- </p>
+ <p>Further details, discussion, and examples, are provided in the
+ <a href="../rewrite/">detailed mod_rewrite documentation</a>.</p>
</div>
<div id="quickview"><h3 class="directives">Directives</h3>
<ul id="toc">
@@ -104,138 +67,104 @@
</ul>
<h3>Topics</h3>
<ul id="topics">
-<li><img alt="" src="../images/down.gif" /> <a href="#Internal">Internal Processing</a></li>
+<li><img alt="" src="../images/down.gif" /> <a href="#InternalAPI">API Phases</a></li>
+<li><img alt="" src="../images/down.gif" /> <a href="#InternalRuleset">Ruleset Processing</a></li>
+<li><img alt="" src="../images/down.gif" /> <a href="#InternalBackRefs">Regex Back-Reference Availability</a></li>
+<li><img alt="" src="../images/down.gif" /> <a href="#quoting">Quoting Special Characters</a></li>
<li><img alt="" src="../images/down.gif" /> <a href="#EnvVar">Environment Variables</a></li>
<li><img alt="" src="../images/down.gif" /> <a href="#Solutions">Practical Solutions</a></li>
</ul></div>
<div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
<div class="section">
-<h2><a name="Internal" id="Internal">Internal Processing</a></h2>
+<h2><a name="InternalAPI" id="InternalAPI">API Phases</a></h2>
- <p>The internal processing of this module is very complex but
- needs to be explained once even to the average user to avoid
- common mistakes and to let you exploit its full
- functionality.</p>
-
-<h3><a name="InternalAPI" id="InternalAPI">API Phases</a></h3>
-
- <p>First you have to understand that when Apache processes a
- HTTP request it does this in phases. A hook for each of these
- phases is provided by the Apache API. Mod_rewrite uses two of
- these hooks: the URL-to-filename translation hook which is
- used after the HTTP request has been read but before any
- authorization starts and the Fixup hook which is triggered
- after the authorization phases and after the per-directory
+ <p>Apache processes a HTTP request in several phases.
+ A hook for each of these
+ phases is provided by the Apache API. <code class="module"><a href="../mod/mod_rewrite.html">mod_rewrite</a></code> uses two of
+ these hooks: the URL-to-filename translation hook
+ (used after the HTTP request has been read, but before any
+ authorization starts) and the Fixup hook (triggered
+ after the authorization phases, and after the per-directory
config files (<code>.htaccess</code>) have been read, but
- before the content handler is activated.</p>
+ before the content handler is activated).</p>
- <p>So, after a request comes in and Apache has determined the
- corresponding server (or virtual server) the rewriting engine
- starts processing of all mod_rewrite directives from the
- per-server configuration in the URL-to-filename phase. A few
- steps later when the final data directories are found, the
+ <p>Once a request comes in, and Apache has determined the
+ appropriate server (or virtual server), the rewrite engine
+ starts the URL-to-filename translation,
+ processing the mod_rewrite directives from the
+ per-server configuration. A few
+ steps later, when the final data directories are found, the
per-directory configuration directives of mod_rewrite are
- triggered in the Fixup phase. In both situations mod_rewrite
- rewrites URLs either to new URLs or to filenames, although
- there is no obvious distinction between them. This is a usage
- of the API which was not intended to be this way when the API
- was designed, but as of Apache 1.x this is the only way
- mod_rewrite can operate. To make this point more clear
- remember the following two points:</p>
-
- <ol>
- <li>Although mod_rewrite rewrites URLs to URLs, URLs to
- filenames and even filenames to filenames, the API
- currently provides only a URL-to-filename hook. In Apache
- 2.0 the two missing hooks will be added to make the
- processing more clear. But this point has no drawbacks for
- the user, it is just a fact which should be remembered:
- Apache does more in the URL-to-filename hook than the API
- intends for it.</li>
-
- <li>
- Unbelievably mod_rewrite provides URL manipulations in
- per-directory context, <em>i.e.</em>, within
- <code>.htaccess</code> files, although these are reached
- a very long time after the URLs have been translated to
- filenames. It has to be this way because
- <code>.htaccess</code> files live in the filesystem, so
- processing has already reached this stage. In other
- words: According to the API phases at this time it is too
- late for any URL manipulations. To overcome this chicken
- and egg problem mod_rewrite uses a trick: When you
- manipulate a URL/filename in per-directory context
- mod_rewrite first rewrites the filename back to its
- corresponding URL (which is usually impossible, but see
- the <code>RewriteBase</code> directive below for the
- trick to achieve this) and then initiates a new internal
- sub-request with the new URL. This restarts processing of
- the API phases.
-
- <p>Again mod_rewrite tries hard to make this complicated
- step totally transparent to the user, but you should
- remember here: While URL manipulations in per-server
- context are really fast and efficient, per-directory
- rewrites are slow and inefficient due to this chicken and
- egg problem. But on the other hand this is the only way
- mod_rewrite can provide (locally restricted) URL
- manipulations to the average user.</p>
- </li>
- </ol>
-
- <p>Don't forget these two points!</p>
+ triggered in the Fixup phase. </p>
-
-<h3><a name="InternalRuleset" id="InternalRuleset">Ruleset Processing</a></h3>
+</div><div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
+<div class="section">
+<h2><a name="InternalRuleset" id="InternalRuleset">Ruleset Processing</a></h2>
- <p>Now when mod_rewrite 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
- kernel for per-directory context). Then the URL rewriting
- engine is started with the contained ruleset (one or more
- rules together with their conditions). The operation of the
- URL rewriting engine itself is exactly the same for both
+ <p>When mod_rewrite is triggered during these two API phases, it
+ reads the relevant rulesets from its configuration
+ structure (which was either created on startup, for
+ per-server context, or during the directory traversal
+ for per-directory context). The URL rewriting
+ engine is started with the appropriate ruleset (one or more
+ rules together with their conditions), and its operation
+ is exactly the same for both
configuration contexts. Only the final result processing is
different. </p>
<p>The order of rules in the ruleset is important because the
- rewriting engine processes them in a special (and not very
- obvious) order. The rule is this: The rewriting engine loops
- through the ruleset rule by rule (<code class="directive"><a href="#rewriterule">RewriteRule</a></code> directives) and
- when a particular rule matches it optionally loops through
- existing corresponding conditions (<code>RewriteCond</code>
+ rewrite engine processes them in a particular (not always
+ obvious) order, as follows: The rewrite engine loops
+ through the rulesets (each ruleset being made up of <code class="directive"><a href="#rewriterule">RewriteRule</a></code> directives, with or without
+ <code class="directive"><a href="#rewritecond">RewriteCond</a></code>s), rule by rule.
+ When a particular rule is matched, <code class="module"><a href="../mod/mod_rewrite.html">mod_rewrite</a></code>
+ also checks the corresponding conditions (<code>RewriteCond</code>
directives). For historical reasons the conditions are given
- first, and so the control flow is a little bit long-winded. See
+ first, making the control flow a little bit long-winded. See
Figure 1 for more details.</p>
<p class="figure">
<img src="../images/mod_rewrite_fig1.gif" width="428" height="385" alt="[Needs graphics capability to display]" /><br />
- <dfn>Figure 1:</dfn>The control flow through the rewriting ruleset
+ <dfn>Figure 1:</dfn>The control flow of the rewrite engine through a
+ rewrite ruleset
</p>
- <p>As you can see, first the URL is matched against the
- <em>Pattern</em> of each rule. When it fails mod_rewrite
- immediately stops processing this rule and continues with the
- next rule. If the <em>Pattern</em> matches, mod_rewrite looks
- for corresponding rule conditions. If none are present, it
- just substitutes the URL with a new value which is
- constructed from the string <em>Substitution</em> and goes on
- with its rule-looping. But if conditions exist, it starts an
- inner loop for processing them in the order that they are
- listed. For conditions the logic is different: we don't match
- a pattern against the current URL. Instead we first create a
- string <em>TestString</em> by expanding variables,
- back-references, map lookups, <em>etc.</em> and then we try
- to match <em>CondPattern</em> against it. If the pattern
- doesn't match, the complete set of conditions and the
- corresponding rule fails. If the pattern matches, then the
- next condition is processed until no more conditions are
+ <p>As above, first the URL is matched against the
+ <em>Pattern</em> of a rule. If it does not match, <code class="module"><a href="../mod/mod_rewrite.html">mod_rewrite</a></code> immediately stops processing that rule,
+ and goes on to the next rule. If the <em>Pattern</em> matches,
+ <code class="module"><a href="../mod/mod_rewrite.html">mod_rewrite</a></code> checks for rule conditions.
+ If none are present, the URL will be replaced with a new string,
+ constructed from the <em>Substitution</em> string, and <code class="module"><a href="../mod/mod_rewrite.html">mod_rewrite</a></code> goes on to the next rule.</p>
+ <p>If <code class="directive">RewriteCond</code>s exist, an
+ inner loop is started, processing them in the order that they are
+ listed. Conditions are not matched against the current URL directly.
+ A <em>TestString</em> is constructed by expanding variables,
+ back-references, map lookups, etc., against which the
+ <em>CondPattern</em> is matched. If the pattern fails to match one
+ of the conditions, the complete set of rule and associated conditions
+ fails. If the pattern matches a given condition, then matching continues
+ to the next condition, until no more conditions are
available. If all conditions match, processing is continued
- with the substitution of the URL with
- <em>Substitution</em>.</p>
+ with the substitution of the <em>Substitution</em> string for the URL.</p>
+</div><div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
+<div class="section">
+<h2><a name="InternalBackRefs" id="InternalBackRefs">Regex Back-Reference Availability</a></h2>
+ <p>Using parentheses in <em>Pattern</em> or in one of the
+ <em>CondPattern</em>s causes back-references to be internally
+ created.
+ These can later be referenced using the strings <code>$N</code> and
+ <code>%N</code> (see below), for creating
+ the <em>Substitution</em> and <em>TestString</em> strings.
+ Figure 2 attempts to show how the back-references are
+ transferred through the process for later expansion.</p>
-<h3><a name="quoting" id="quoting">Quoting Special Characters</a></h3>
+<p class="figure">
+ <img src="../images/mod_rewrite_fig2.gif" width="381" height="179" alt="[Needs graphics capability to display]" /><br />
+ <dfn>Figure 2:</dfn> The back-reference flow through a rule.
+</p>
+</div><div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
+<div class="section">
+<h2><a name="quoting" id="quoting">Quoting Special Characters</a></h2>
<p>As of Apache 1.3.20, special characters in
<em>TestString</em> and <em>Substitution</em> strings can be
@@ -245,29 +174,6 @@
dollar-sign character in a <em>Substitution</em> string by
using '<code>\$</code>'; this keeps mod_rewrite from trying
to treat it as a backreference.</p>
-
-
-<h3><a name="InternalBackRefs" id="InternalBackRefs">Regex Back-Reference Availability</a></h3>
-
- <p>One important thing here has to be remembered: Whenever you
- use parentheses in <em>Pattern</em> or in one of the
- <em>CondPattern</em>, back-references are internally created
- which can be used with the strings <code>$N</code> and
- <code>%N</code> (see below). These are available for creating
- the strings <em>Substitution</em> and <em>TestString</em>.
- Figure 2 shows to which locations the back-references are
- transfered for expansion.</p>
-
-<p class="figure">
- <img src="../images/mod_rewrite_fig2.gif" width="381" height="179" alt="[Needs graphics capability to display]" /><br />
- <dfn>Figure 2:</dfn> The back-reference flow through a rule.
-</p>
- <p>We know this was a crash course on mod_rewrite's internal
- processing. But you will benefit from this knowledge when
- reading the following documentation of the available
- directives.</p>
-
-
</div><div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
<div class="section">
<h2><a name="EnvVar" id="EnvVar">Environment Variables</a></h2>
@@ -281,8 +187,8 @@
System-view. </p>
<p>Notice: These variables hold the URI/URL <em>as they were
- initially requested</em>, <em>i.e.</em>, <em>before</em> any
- rewriting. This is important because the rewriting process is
+ initially requested</em>, that is, <em>before</em> any
+ rewriting. This is important to note because the rewriting process is
primarily used to rewrite logical URLs to physical
pathnames.</p>
@@ -297,11 +203,11 @@
<div class="section">
<h2><a name="Solutions" id="Solutions">Practical Solutions</a></h2>
- <p>We also have an <a href="../misc/rewriteguide.html">URL
- Rewriting Guide</a> available, which provides a collection of
- practical solutions for URL-based problems. There you can
- find real-life rulesets and additional information about
- mod_rewrite.</p>
+ <p>For numerous examples of common, and not-so-common, uses for
+ mod_rewrite, see the <a href="../rewrite/rewrite_guide.html">Rewrite
+ Guide</a>, and the <a href="../rewrite/rewrite_guide_advanced.html">Advanced Rewrite
+ Guide</a> documents.</p>
+
</div>
<div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
<div class="directive-section"><h2><a name="RewriteBase" id="RewriteBase">RewriteBase</a> <a name="rewritebase" id="rewritebase">Directive</a></h2>
@@ -318,26 +224,26 @@
sets the base URL for per-directory rewrites. As you will see
below, <code class="directive"><a href="#rewriterule">RewriteRule</a></code>
can be used in per-directory config files
- (<code>.htaccess</code>). There it will act locally,
- <em>i.e.</em>, the local directory prefix is stripped at this
- stage of processing and your rewriting rules act only on the
- remainder. At the end it is automatically added back to the
+ (<code>.htaccess</code>). In such a case, it will act locally,
+ stripping the local directory prefix before processing, and applying
+ rewrite rules only to the remainder. When processing is complete, the
+ prefix is automatically added back to the
path. The default setting is; <code class="directive">RewriteBase</code> <em>physical-directory-path</em></p>
<p>When a substitution occurs for a new URL, this module has
to re-inject the URL into the server processing. To be able
to do this it needs to know what the corresponding URL-prefix
or URL-base is. By default this prefix is the corresponding
- filepath itself. <strong>But at most websites URLs are NOT
+ filepath itself. <strong>However, for most websites, URLs are NOT
directly related to physical filename paths, so this
- assumption will usually be wrong!</strong> There you have to
+ assumption will often be wrong!</strong> Therefore, you can
use the <code>RewriteBase</code> directive to specify the
correct URL-prefix.</p>
<div class="note"> If your webserver's URLs are <strong>not</strong> directly
-related to physical file paths, you have to use
+related to physical file paths, you will need to use
<code class="directive">RewriteBase</code> in every <code>.htaccess</code>
-files where you want to use <code class="directive"><a href="#rewriterule">RewriteRule</a></code> directives.
+file where you want to use <code class="directive"><a href="#rewriterule">RewriteRule</a></code> directives.
</div>
<p> For example, assume the following per-directory config file:</p>
@@ -379,17 +285,15 @@
Result:
/abc/def/newstuff.html
</pre>
- <p>This seems very complicated but is
- the correct Apache internal processing, because the
- per-directory rewriting comes too late in the
- process. So, when it occurs the (rewritten) request
- has to be re-injected into the Apache kernel! BUT:
- While this seems like a serious overhead, it really
- isn't, because this re-injection happens fully
- internally to the Apache server and the same
- procedure is used by many other operations inside
- Apache. So, you can be sure the design and
- implementation is correct.</p>
+ <p>This seems very complicated, but is in fact
+ correct Apache internal processing. Because the
+ per-directory rewriting comes late in the
+ process, the rewritten request
+ has to be re-injected into the Apache kernel.
+ This is not the serious overhead it may seem to be -
+ this re-injection is completely internal to the
+ Apache server (and the same procedure is used by
+ many other operations within Apache).</p>
</div>
@@ -407,62 +311,42 @@
<tr><th><a href="directive-dict.html#Module">Module:</a></th><td>mod_rewrite</td></tr>
</table>
<p>The <code class="directive">RewriteCond</code> directive defines a
- rule condition. Precede a <code class="directive"><a href="#rewriterule">RewriteRule</a></code> directive with one
- or more <code class="directive">RewriteCond</code> directives. The following
- rewriting rule is only used if its pattern matches the current
- state of the URI <strong>and</strong> if these additional
- conditions apply too.</p>
+ rule condition. One or more <code class="directive">RewriteCond</code>
+ can precede a <code class="directive"><a href="#rewriterule">RewriteRule</a></code>
+ directive. The following rule is then only used if both
+ the current state of the URI matches its pattern, <strong>and</strong> if these conditions are met.</p>
- <p><em>TestString</em> is a string which can contains the
+ <p><em>TestString</em> is a string which can contain the
following expanded constructs in addition to plain text:</p>
<ul>
<li>
<strong>RewriteRule backreferences</strong>: These are
- backreferences of the form
-
- <p class="indent">
- <strong><code>$N</code></strong>
- </p>
- (0 <= N <= 9) which provide access to the grouped
- parts (parenthesis!) of the pattern from the
- corresponding <code>RewriteRule</code> directive (the one
- following the current bunch of <code>RewriteCond</code>
- directives).
+ backreferences of the form <strong><code>$N</code></strong>
+ (0 <= N <= 9), which provide access to the grouped
+ parts (in parentheses) of the pattern, from the
+ <code>RewriteRule</code> which is subject to the current
+ set of <code>RewriteCond</code> conditions..
</li>
-
<li>
<strong>RewriteCond backreferences</strong>: These are
- backreferences of the form
-
- <p class="indent">
- <strong><code>%N</code></strong>
- </p>
- (1 <= N <= 9) which provide access to the grouped
- parts (parentheses!) of the pattern from the last matched
- <code>RewriteCond</code> directive in the current bunch
+ backreferences of the form <strong><code>%N</code></strong>
+ (1 <= N <= 9), which provide access to the grouped
+ parts (again, in parentheses) of the pattern, from the last matched
+ <code>RewriteCond</code> in the current set
of conditions.
</li>
-
<li>
<strong>RewriteMap expansions</strong>: These are
- expansions of the form
-
- <p class="indent">
- <strong><code>${mapname:key|default}</code></strong>
- </p>
+ expansions of the form <strong><code>${mapname:key|default}</code></strong>.
See <a href="#mapfunc">the documentation for
RewriteMap</a> for more details.
</li>
-
<li>
<strong>Server-Variables</strong>: These are variables of
the form
-
- <p class="indent">
<strong><code>%{</code> <em>NAME_OF_VARIABLE</em>
<code>}</code></strong>
- </p>
where <em>NAME_OF_VARIABLE</em> can be a string taken
from the following list:
@@ -486,7 +370,8 @@
<td>
REMOTE_ADDR<br />
REMOTE_HOST<br />
- REMOTE_USER<br />
+ REMOTE_PORT<br />
+ REMOTE_USER<br />
REMOTE_IDENT<br />
REQUEST_METHOD<br />
SCRIPT_FILENAME<br />
@@ -535,15 +420,14 @@
</tr>
</table>
-<div class="note">
<p>These variables all
correspond to the similarly named HTTP
MIME-headers, C variables of the Apache server or
<code>struct tm</code> fields of the Unix system.
Most are documented elsewhere in the Manual or in
the CGI specification. Those that are special to
- mod_rewrite include:</p>
-
+ mod_rewrite include those below.</p>
+ <div class="note">
<dl>
<dt><code>IS_SUBREQ</code></dt>
@@ -587,7 +471,7 @@
<dd>Will contain the text "on" if the connection is
using SSL/TLS, or "off" otherwise. (This variable
- can be safely used regardless of whether
+ can be safely used regardless of whether or not
<code class="module"><a href="../mod/mod_ssl.html">mod_ssl</a></code> is loaded).</dd>
</dl>
@@ -595,69 +479,72 @@
</li>
</ul>
- <p>Special Notes:</p>
+ <p>Other things you should be aware of:</p>
<ol>
<li>The variables SCRIPT_FILENAME and REQUEST_FILENAME
- contain the same value, <em>i.e.</em>, the value of the
+ contain the same value - the value of the
<code>filename</code> field of the internal
<code>request_rec</code> structure of the Apache server.
- The first name is just the commonly known CGI variable name
- while the second is the consistent counterpart to
+ The first name is the commonly known CGI variable name
+ while the second is the appropriate counterpart of
REQUEST_URI (which contains the value of the
<code>uri</code> field of <code>request_rec</code>).</li>
- <li>There is the special format:
- <code>%{ENV:variable}</code> where <em>variable</em> can be
- any environment variable. This is looked-up via internal
+ <li>
+ <code>%{ENV:variable}</code>, where <em>variable</em> can be
+ any environment variable, is also available.
+ This is looked-up via internal
Apache structures and (if not found there) via
<code>getenv()</code> from the Apache server process.</li>
- <li>There is the special format:
- <code>%{SSL:variable}</code> where <em>variable</em> is the
+ <li>
+ <code>%{SSL:variable}</code>, where <em>variable</em> is the
name of an <a href="mod_ssl.html#envvars">SSL environment
- variable</a>; this can be used whether or not
+ variable</a>, can be used whether or not
<code class="module"><a href="../mod/mod_ssl.html">mod_ssl</a></code> is loaded, but will always expand to
the empty string if it is not. Example:
<code>%{SSL:SSL_CIPHER_USEKEYSIZE}</code> may expand to
<code>128</code>.</li>
- <li>There is the special format:
- <code>%{HTTP:header}</code> where <em>header</em> can be
- any HTTP MIME-header name. This is looked-up from the HTTP
- request. Example: <code>%{HTTP:Proxy-Connection}</code> is
+ <li>
+ <code>%{HTTP:header}</code>, where <em>header</em> can be
+ any HTTP MIME-header name, can always be used to obtain the
+ value of a header sent in the HTTP request.
+ Example: <code>%{HTTP:Proxy-Connection}</code> is
the value of the HTTP header
``<code>Proxy-Connection:</code>''.</li>
- <li>There is the special format
- <code>%{LA-U:variable}</code> for look-aheads which perform
+ <li>
+ <code>%{LA-U:variable}</code> can be used for look-aheads which perform
an internal (URL-based) sub-request to determine the final
- value of <em>variable</em>. Use this when you want to use a
- variable for rewriting which is actually set later in an
- API phase and thus is not available at the current stage.
- For instance when you want to rewrite according to the
+ value of <em>variable</em>. This can be used to access
+ variable for rewriting which is not available at the current
+ stage, but will be set in a later phase.
+ <p>For instance, to rewrite according to the
<code>REMOTE_USER</code> variable from within the
- per-server context (<code>httpd.conf</code> file) you have
- to use <code>%{LA-U:REMOTE_USER}</code> because this
- variable is set by the authorization phases which come
- <em>after</em> the URL translation phase where mod_rewrite
- operates. On the other hand, because mod_rewrite implements
+ per-server context (<code>httpd.conf</code> file) you must
+ use <code>%{LA-U:REMOTE_USER}</code> - this
+ variable is set by the authorization phases, which come
+ <em>after</em> the URL translation phase (during which mod_rewrite
+ operates).</p>
+ <p>On the other hand, because mod_rewrite implements
its per-directory context (<code>.htaccess</code> file) via
the Fixup phase of the API and because the authorization
phases come <em>before</em> this phase, you just can use
- <code>%{REMOTE_USER}</code> there.</li>
+ <code>%{REMOTE_USER}</code> in that context.</p></li>
- <li>There is the special format:
- <code>%{LA-F:variable}</code> which performs an internal
- (filename-based) sub-request to determine the final value
- of <em>variable</em>. Most of the time this is the same as
+ <li>
+ <code>%{LA-F:variable}</code> can be used to perform an internal
+ (filename-based) sub-request, to determine the final value
+ of <em>variable</em>. Most of the time, this is the same as
LA-U above.</li>
</ol>
<p><em>CondPattern</em> is the condition pattern,
- <em>i.e.</em>, a regular expression which is applied to the
- current instance of the <em>TestString</em>, <em>i.e.</em>,
- <em>TestString</em> is evaluated and then matched against
+ a regular expression which is applied to the
+ current instance of the <em>TestString</em>.
+ <em>TestString</em> is first evaluated, before being matched against
<em>CondPattern</em>.</p>
<p><strong>Remember:</strong> <em>CondPattern</em> is a
@@ -675,92 +562,88 @@
use one of the following:
<ul>
- <li>'<strong><CondPattern</strong>' (is lexically
- lower)<br />
- Treats the <em>CondPattern</em> as a plain string and
- compares it lexically to <em>TestString</em>. True if
- <em>TestString</em> is lexically lower than
+
+ <li>'<strong><CondPattern</strong>' (lexicographically
+ precedes)<br />
+ Treats the <em>CondPattern</em> as a plain string and
+ compares it lexicographically to <em>TestString</em>. True if
+ <em>TestString</em> lexicographically precedes
<em>CondPattern</em>.</li>
- <li>'<strong>>CondPattern</strong>' (is lexically
- greater)<br />
- Treats the <em>CondPattern</em> as a plain string and
- compares it lexically to <em>TestString</em>. True if
- <em>TestString</em> is lexically greater than
- <em>CondPattern</em>.</li>
+ <li>'<strong>>CondPattern</strong>' (lexicographically
+ follows)<br />
+ Treats the <em>CondPattern</em> as a plain string and
+ compares it lexicographically to <em>TestString</em>. True if
+ <em>TestString</em> lexicographically follows
+ <em>CondPattern</em>.</li>
- <li>'<strong>=CondPattern</strong>' (is lexically
+ <li>'<strong>=CondPattern</strong>' (lexicographically
equal)<br />
- Treats the <em>CondPattern</em> as a plain string and
- compares it lexically to <em>TestString</em>. True if
- <em>TestString</em> is lexically equal to
- <em>CondPattern</em>, i.e the two strings are exactly
- equal (character by character). If <em>CondPattern</em>
- is just <code>""</code> (two quotation marks) this
+ Treats the <em>CondPattern</em> as a plain string and
+ compares it lexicographically to <em>TestString</em>. True if
+ <em>TestString</em> is lexicographically equal to
+ <em>CondPattern</em> (the two strings are exactly
+ equal, character for character). If <em>CondPattern</em>
+ is <code>""</code> (two quotation marks) this
compares <em>TestString</em> to the empty string.</li>
<li>'<strong>-d</strong>' (is
<strong>d</strong>irectory)<br />
Treats the <em>TestString</em> as a pathname and tests
- if it exists and is a directory.</li>
+ whether or not it exists, and is a directory.</li>
<li>'<strong>-f</strong>' (is regular
<strong>f</strong>ile)<br />
Treats the <em>TestString</em> as a pathname and tests
- if it exists and is a regular file.</li>
+ whether or not it exists, and is a regular file.</li>
- <li>'<strong>-s</strong>' (is regular file with
+ <li>'<strong>-s</strong>' (is regular file, with
<strong>s</strong>ize)<br />
- Treats the <em>TestString</em> as a pathname and tests
- if it exists and is a regular file with size greater
+ Treats the <em>TestString</em> as a pathname and tests
+ whether or not it exists, and is a regular file with size greater
than zero.</li>
<li>'<strong>-l</strong>' (is symbolic
<strong>l</strong>ink)<br />
- Treats the <em>TestString</em> as a pathname and tests
- if it exists and is a symbolic link.</li>
+ Treats the <em>TestString</em> as a pathname and tests
+ whether or not it exists, and is a symbolic link.</li>
- <li>'<strong>-F</strong>' (is existing file via
+ <li>'<strong>-F</strong>' (is existing file, via
subrequest)<br />
- Checks if <em>TestString</em> is a valid file and
+ Checks whether or not <em>TestString</em> is a valid file,
accessible via all the server's currently-configured
access controls for that path. This uses an internal
- subrequest to determine the check, so use it with care
- because it decreases your servers performance!</li>
+ subrequest to do the check, so use it with care -
+ it can impact your server's performance!</li>
- <li>'<strong>-U</strong>' (is existing URL via
+ <li>'<strong>-U</strong>' (is existing URL, via
subrequest)<br />
- Checks if <em>TestString</em> is a valid URL and
+ Checks whether or not <em>TestString</em> is a valid URL,
accessible via all the server's currently-configured
access controls for that path. This uses an internal
- subrequest to determine the check, so use it with care
- because it decreases your server's performance!</li>
+ subrequest to do the check, so use it with care -
+ it can impact your server's performance!</li>
</ul>
-<div class="note"><h3>Notice</h3>
+<div class="note"><h3>Note</h3>
All of these tests can
also be prefixed by an exclamation mark ('!') to
negate their meaning.
</div>
</li>
- </ol>
-
- <p>Additionally you can set special flags for
- <em>CondPattern</em> by appending</p>
- <p class="indent">
+ <li>You can also set special flags for
+ <em>CondPattern</em> by appending
<strong><code>[</code><em>flags</em><code>]</code></strong>
- </p>
-
- <p>as the third argument to the <code>RewriteCond</code>
- directive. <em>Flags</em> is a comma-separated list of the
- following flags:</p>
+ as the third argument to the <code>RewriteCond</code>
+ directive, where <em>flags</em> is a comma-separated list of any of the
+ following flags:
<ul>
<li>'<strong><code>nocase|NC</code></strong>'
(<strong>n</strong>o <strong>c</strong>ase)<br />
- This makes the test case-insensitive, <em>i.e.</em>, there
- is no difference between 'A-Z' and 'a-z' both in the
+ This makes the test case-insensitive - differences
+ between 'A-Z' and 'a-z' are ignored, both in the
expanded <em>TestString</em> and the <em>CondPattern</em>.
This flag is effective only for comparisons between
<em>TestString</em> and <em>CondPattern</em>. It has no
@@ -769,8 +652,8 @@
<li>
'<strong><code>ornext|OR</code></strong>'
(<strong>or</strong> next condition)<br />
- Use this to combine rule conditions with a local OR
- instead of the implicit AND. Typical example:
+ Use this to combine rule conditions with a local OR
+ instead of the implicit AND. Typical example:
<div class="example"><pre>
RewriteCond %{REMOTE_HOST} ^host1.* [OR]
@@ -779,10 +662,12 @@
RewriteRule ...some special stuff for any of these hosts...
</pre></div>
- Without this flag you would have to write the cond/rule
- three times.
+ Without this flag you would have to write the condition/rule
+ pair three times.
</li>
</ul>
+ </li>
+ </ol>
<p><strong>Example:</strong></p>
@@ -800,13 +685,16 @@
RewriteRule ^/$ /homepage.std.html [L]
</pre></div>
- <p>Interpretation: If you use Netscape Navigator as your
- browser (which identifies itself as 'Mozilla'), then you
- get the max homepage, which includes Frames, <em>etc.</em>
- If you use the Lynx browser (which is Terminal-based), then
- you get the min homepage, which contains no images, no
- tables, <em>etc.</em> If you use any other browser you get
- the standard homepage.</p>
+ <p>Explanation: If you use a browser which identifies itself
+ as 'Mozilla' (including Netscape Navigator, Mozilla etc), then you
+ get the max homepage (which could include frames, or other special
+ features).
+ If you use the Lynx browser (which is terminal-based), then
+ you get the min homepage (which could be a version designed for
+ easy, text-only browsing).
+ If neither of these conditions apply (you use any other browser,
+ or your browser identifies itself as something non-standard), you get
+ the std (standard) homepage.</p>
</div>
@@ -886,7 +774,7 @@
<div class="note"><h3>Security</h3>
See the <a href="../misc/security_tips.html">Apache Security Tips</a>
-document for details on why your security could be compromised if the
+document for details on how your security could be compromised if the
directory where logfiles are stored is writable by anyone other than
the user that starts the server.
</div>
@@ -960,7 +848,7 @@
<code>}</code></strong>
</p>
- <p>When such a construct occurs the map <em>MapName</em> is
+ <p>When such a construct occurs, the map <em>MapName</em> is
consulted and the key <em>LookupKey</em> is looked-up. If the
key is found, the map-function construct is substituted by
<em>SubstValue</em>. If the key is not found then it is
@@ -1101,23 +989,23 @@
MapType: <code>int</code>, MapSource: Internal Apache
function
- <p>Here the source is an internal Apache function.
+ <p>Here, the source is an internal Apache function.
Currently you cannot create your own, but the following
- functions already exists:</p>
+ functions already exist:</p>
<ul>
<li><strong>toupper</strong>:<br />
- Converts the looked up key to all upper case.</li>
+ Converts the key to all upper case.</li>
<li><strong>tolower</strong>:<br />
- Converts the looked up key to all lower case.</li>
+ Converts the key to all lower case.</li>
<li><strong>escape</strong>:<br />
- Translates special characters in the looked up key to
+ Translates special characters in the key to
hex-encodings.</li>
<li><strong>unescape</strong>:<br />
- Translates hex-encodings in the looked up key back to
+ Translates hex-encodings in the key back to
special characters.</li>
</ul>
</li>
@@ -1128,15 +1016,15 @@
path to valid regular file
<p>Here the source is a program, not a map file. To
- create it you can use the language of your choice, but
- the result has to be a executable (<em>i.e.</em>, either
+ create it you can use a language of your choice, but
+ the result has to be an executable program (either
object-code or a script with the magic cookie trick
'<code>#!/path/to/interpreter</code>' as the first
line).</p>
- <p>This program is started once at startup of the Apache
- servers and then communicates with the rewriting engine
- over its <code>stdin</code> and <code>stdout</code>
+ <p>This program is started once, when the Apache server
+ is started, and then communicates with the rewriting engine
+ via its <code>stdin</code> and <code>stdout</code>
file-handles. For each map-function lookup it will
receive the key to lookup as a newline-terminated string
on <code>stdin</code>. It then has to give back the
@@ -1159,17 +1047,17 @@
<p>But be very careful:</p>
<ol>
- <li>``<em>Keep it simple, stupid</em>'' (KISS), because
- if this program hangs it will hang the Apache server
- when the rule occurs.</li>
-
- <li>Avoid one common mistake: never do buffered I/O on
- <code>stdout</code>! This will cause a deadloop! Hence
- the ``<code>$|=1</code>'' in the above example...</li>
-
- <li>Use the <code class="directive"><a href="#rewritelock">RewriteLock</a></code> directive to
- define a lockfile mod_rewrite can use to synchronize the
- communication to the program. By default no such
+ <li>``<em>Keep it simple, stupid</em>'' (KISS).
+ If this program hangs, it will cause Apache to hang
+ when trying to use the relevant rewrite rule.</li>
+
+ <li>A common mistake is to use buffered I/O on
+ <code>stdout</code>. Avoid this, as it will cause a deadloop!
+ ``<code>$|=1</code>'' is used above, to prevent this.</li>
+
+ <li>The <code class="directive"><a href="#rewritelock">RewriteLock</a></code> directive can
+ be used to define a lockfile which mod_rewrite can use to synchronize
+ communication with the mapping program. By default no such
synchronization takes place.</li>
</ol>
</li>
@@ -1242,55 +1130,53 @@
<tr><th><a href="directive-dict.html#Compatibility">Compatibility:</a></th><td>The cookie-flag is available in Apache 2.0.40 and later.</td></tr>
</table>
<p>The <code class="directive">RewriteRule</code> directive is the real
- rewriting workhorse. The directive can occur more than once.
- Each directive then defines one single rewriting rule. The
- <strong>definition order</strong> of these rules is
- <strong>important</strong>, because this order is used when
- applying the rules at run-time.</p>
+ rewriting workhorse. The directive can occur more than once, with
+ each instance defining a single rewrite rule. The
+ order in which these rules are defined is important - this is the order
+ in which they will be applied at run-time.</p>
<p><a id="patterns" name="patterns"><em>Pattern</em></a> is
a perl compatible <a id="regexp" name="regexp">regular
- expression</a> which gets applied to the current URL. Here
- ``current'' means the value of the URL when this rule gets
+ expression</a>, which is applied to the current URL.
+ ``Current'' means the value of the URL when this rule is
applied. This may not be the originally requested URL,
- because any number of rules may already have matched and made
- alterations to it.</p>
+ which may already have matched a previous rule, and have
+ been altered.</p>
- <p>Some hints about the syntax of regular expressions:</p>
+ <p>Some hints on the syntax of regular expressions:</p>
<div class="note"><pre>
<strong>Text:</strong>
<strong><code>.</code></strong> Any single character
- <strong><code>[</code></strong>chars<strong><code>]</code></strong> Character class: One of chars
- <strong><code>[^</code></strong>chars<strong><code>]</code></strong> Character class: None of chars
+ <strong><code>[</code></strong>chars<strong><code>]</code></strong> Character class: Any character of the class ``chars''
+ <strong><code>[^</code></strong>chars<strong><code>]</code></strong> Character class: Not a character of the class ``chars''
text1<strong><code>|</code></strong>text2 Alternative: text1 or text2
<strong>Quantifiers:</strong>
- <strong><code>?</code></strong> 0 or 1 of the preceding text
- <strong><code>*</code></strong> 0 or N of the preceding text (N > 0)
- <strong><code>+</code></strong> 1 or N of the preceding text (N > 1)
+ <strong><code>?</code></strong> 0 or 1 occurrences of the preceding text
+ <strong><code>*</code></strong> 0 or N occurrences of the preceding text (N > 0)
+ <strong><code>+</code></strong> 1 or N occurrences of the preceding text (N > 1)
<strong>Grouping:</strong>
<strong><code>(</code></strong>text<strong><code>)</code></strong> Grouping of text
- (either to set the borders of an alternative or
- for making backreferences where the <strong>N</strong>th group can
- be used on the RHS of a RewriteRule with <code>$</code><strong>N</strong>)
+ (used either to set the borders of an alternative as above, or
+ to make backreferences, where the <strong>N</strong>th group can
+ be referred to on the RHS of a RewriteRule as <code>$</code><strong>N</strong>)
<strong>Anchors:</strong>
- <strong><code>^</code></strong> Start of line anchor
- <strong><code>$</code></strong> End of line anchor
+ <strong><code>^</code></strong> Start-of-line anchor
+ <strong><code>$</code></strong> End-of-line anchor
<strong>Escaping:</strong>
- <strong><code>\</code></strong>char escape that particular char
- (for instance to specify the chars "<code>.[]()</code>" <em>etc.</em>)
+ <strong><code>\</code></strong>char escape the given char
+ (for instance, to specify the chars "<code>.[]()</code>" <em>etc.</em>)
</pre></div>
- <p>For more information about regular expressions have a look at the
+ <p>For more information about regular expressions, have a look at the
perl regular expression manpage ("<a href="http://www.perldoc.com/perl5.6.1/pod/perlre.html">perldoc
perlre</a>"). If you are interested in more detailed
information about regular expressions and their variants
- (POSIX regex <em>etc.</em>) have a look at the
- following dedicated book on this topic:</p>
+ (POSIX regex etc.) the following book is dedicated to this topic:</p>
<p class="indent">
<em>Mastering Regular Expressions, 2nd Edition</em><br />
@@ -1299,34 +1185,32 @@
ISBN 0-596-00289-0<br />
</p>
- <p>Additionally in mod_rewrite the NOT character
- ('<code>!</code>') is a possible pattern prefix. This gives
- you the ability to negate a pattern; to say, for instance:
+ <p>In mod_rewrite, the NOT character
+ ('<code>!</code>') is also available as a possible pattern
+ prefix. This enables you to negate a pattern; to say, for instance:
``<em>if the current URL does <strong>NOT</strong> match this
pattern</em>''. This can be used for exceptional cases, where
it is easier to match the negative pattern, or as a last
default rule.</p>
-<div class="note"><h3>Notice</h3>
-When using the NOT character
- to negate a pattern you cannot have grouped wildcard
- parts in the pattern. This is impossible because when the
- pattern does NOT match, there are no contents for the
- groups. In consequence, if negated patterns are used, you
- cannot use <code>$N</code> in the substitution
- string!
+<div class="note"><h3>Note</h3>
+When using the NOT character to negate a pattern, you cannot include
+grouped wildcard parts in that pattern. This is because, when the
+pattern does NOT match (ie, the negation matches), there are no
+contents for the groups. Thus, if negated patterns are used, you
+cannot use <code>$N</code> in the substitution string!
</div>
- <p><a id="rhs" name="rhs"><em>Substitution</em></a> of a
- rewriting rule is the string which is substituted for (or
- replaces) the original URL for which <em>Pattern</em>
- matched. Beside plain text you can use</p>
+ <p>The <a id="rhs" name="rhs"><em>substitution</em></a> of a
+ rewrite rule is the string which is substituted for (or
+ replaces) the original URL which <em>Pattern</em>
+ matched. In addition to plain text, it can include</p>
<ol>
- <li>back-references <code>$N</code> to the RewriteRule
+ <li>back-references (<code>$N</code>) to the RewriteRule
pattern</li>
- <li>back-references <code>%N</code> to the last matched
+ <li>back-references (<code>%N</code>) to the last matched
RewriteCond pattern</li>
<li>server-variables as in rule condition test-strings
@@ -1335,73 +1219,38 @@
<li><a href="#mapfunc">mapping-function</a> calls
(<code>${mapname:key|default}</code>)</li>
</ol>
- <p>Back-references are <code>$</code><strong>N</strong>
- (<strong>N</strong>=0..9) identifiers which will be replaced
+
+ <p>Back-references are identifiers of the form
+ <code>$</code><strong>N</strong>
+ (<strong>N</strong>=0..9), which will be replaced
by the contents of the <strong>N</strong>th group of the
matched <em>Pattern</em>. The server-variables are the same
as for the <em>TestString</em> of a <code>RewriteCond</code>
directive. The mapping-functions come from the
<code>RewriteMap</code> directive and are explained there.
- These three types of variables are expanded in the order of
- the above list. </p>
+ These three types of variables are expanded in the order above.</p>
- <p>As already mentioned above, all the rewriting rules are
- applied to the <em>Substitution</em> (in the order of
- definition in the config file). The URL is <strong>completely
+ <p>As already mentioned, all rewrite rules are
+ applied to the <em>Substitution</em> (in the order in which
+ they are defined
+ in the config file). The URL is <strong>completely
replaced</strong> by the <em>Substitution</em> and the
- rewriting process goes on until there are no more rules
- unless explicitly terminated by a
+ rewriting process continues until all rules have been applied,
+ or it is explicitly terminated by a
<code><strong>L</strong></code> flag - see below.</p>
<p>There is a special substitution string named
'<code>-</code>' which means: <strong>NO
- substitution</strong>! Sounds silly? No, it is useful to
- provide rewriting rules which <strong>only</strong> match
- some URLs but do no substitution, <em>e.g.</em>, in
- conjunction with the <strong>C</strong> (chain) flag to be
- able to have more than one pattern to be applied before a
- substitution occurs.</p>
-
-<div class="note"><h3>Query String</h3>
- <p>The <em>Pattern</em> will not match against the query string.
- Instead, you must use a <code class="directive"><a href="#rewritecond">RewriteCond</a></code> with the
- <code>%{QUERY_STRING}</code> variable. You can, however, create
- URLs in the substitution string containing a query string
- part. Just use a question mark inside the substitution string to
- indicate that the following stuff should be re-injected into the
- query string. When you want to erase an existing query string,
- end the substitution string with just the question mark. To
- combine a new query string with an old one, use the
- <code>[QSA]</code> flag (see below).</p>
-</div>
-
-<div class="note"><h3>Substitution of Absolute URLs</h3>
- <p>There is a special feature:
- When you prefix a substitution field with
- <code>http://</code><em>thishost</em>[<em>:thisport</em>]
- then <strong>mod_rewrite</strong> automatically strips it
- out. This auto-reduction on implicit external redirect
- URLs is a useful and important feature when used in
- combination with a mapping-function which generates the
- hostname part. Have a look at the first example in the
- example section below to understand this.</p>
-
- <p><strong>Remember:</strong> An unconditional external
- redirect to your own server will not work with the prefix
- <code>http://thishost</code> because of this feature. To
- achieve such a self-redirect, you have to use the
- <strong>R</strong>-flag (see below).</p>
-</div>
+ substitution</strong>! This is useful in providing
+ rewriting rules which <strong>only</strong> match
+ URLs but do not substitute anything for them. It is commonly used
+ in conjunction with the <strong>C</strong> (chain) flag, in order
+ to apply more than one pattern before substitution occurs.</p>
- <p>Additionally you can set special flags for
- <em>Substitution</em> by appending</p>
-
- <p class="indent">
- <strong><code>[</code><em>flags</em><code>]</code></strong>
- </p>
- <p>
+ <p>Additionally you can set special <a name="rewriteflags" id="rewriteflags">flags</a> for <em>Substitution</em> by
+ appending <strong><code>[</code><em>flags</em><code>]</code></strong>
as the third argument to the <code>RewriteRule</code>
- directive. <em>Flags</em> is a comma-separated list of the
+ directive. <em>Flags</em> is a comma-separated list of any of the
following flags: </p>
<ul>
@@ -1409,61 +1258,60 @@
(<strong>c</strong>hained with next rule)<br />
This flag chains the current rule with the next rule
(which itself can be chained with the following rule,
- <em>etc.</em>). This has the following effect: if a rule
- matches, then processing continues as usual, <em>i.e.</em>,
+ and so on). This has the following effect: if a rule
+ matches, then processing continues as usual -
the flag has no effect. If the rule does
<strong>not</strong> match, then all following chained
- rules are skipped. For instance, use it to remove the
- ``<code>.www</code>'' part inside a per-directory rule set
+ rules are skipped. For instance, it can be used to remove the
+ ``<code>.www</code>'' part, inside a per-directory rule set,
when you let an external redirect happen (where the
- ``<code>.www</code>'' part should not to occur!).</li>
+ ``<code>.www</code>'' part should not occur!).</li>
<li>
'<strong><code>cookie|CO=</code></strong><em>NAME</em>:<em>VAL</em>:<em>domain</em>[:<em>lifetime</em>[:<em>path</em>]]'
(set <strong>co</strong>okie)<br />
- This sets a cookie on the client's browser. The cookie's name
+ This sets a cookie in the client's browser. The cookie's name
is specified by <em>NAME</em> and the value is
<em>VAL</em>. The <em>domain</em> field is the domain of the
- cookie, such as '.apache.org',the optional <em>lifetime</em>
+ cookie, such as '.apache.org', the optional <em>lifetime</em>
is the lifetime of the cookie in minutes, and the optional
<em>path</em> is the path of the cookie</li>
<li>
'<strong><code>env|E=</code></strong><em>VAR</em>:<em>VAL</em>'
(set <strong>e</strong>nvironment variable)<br />
- This forces an environment variable named <em>VAR</em> to
+ This forces an environment variable named <em>VAR</em> to
be set to the value <em>VAL</em>, where <em>VAL</em> can
- contain regexp backreferences <code>$N</code> and
- <code>%N</code> which will be expanded. You can use this
- flag more than once to set more than one variable. The
- variables can be later dereferenced in many situations, but
- usually from within XSSI (via <code><!--#echo
- var="VAR"--></code>) or CGI (<em>e.g.</em>
- <code>$ENV{'VAR'}</code>). Additionally you can dereference
- it in a following RewriteCond pattern via
- <code>%{ENV:VAR}</code>. Use this to strip but remember
- information from URLs.</li>
+ contain regexp backreferences (<code>$N</code> and
+ <code>%N</code>) which will be expanded. You can use this
+ flag more than once, to set more than one variable. The
+ variables can later be dereferenced in many situations, most commonly
+ from within XSSI (via <code><!--#echo
+ var="VAR"--></code>) or CGI (<code>$ENV{'VAR'}</code>).
+ You can also dereference the variable in a later RewriteCond pattern, using
+ <code>%{ENV:VAR}</code>. Use this to strip
+ information from URLs, while maintaining a record of that information.</li>
<li>'<strong><code>forbidden|F</code></strong>' (force URL
to be <strong>f</strong>orbidden)<br />
- This forces the current URL to be forbidden,
- <em>i.e.</em>, it immediately sends back a HTTP response of
- 403 (FORBIDDEN). Use this flag in conjunction with
+ This forces the current URL to be forbidden - it immediately
+ sends back a HTTP response of 403 (FORBIDDEN).
+ Use this flag in conjunction with
appropriate RewriteConds to conditionally block some
URLs.</li>
<li>'<strong><code>gone|G</code></strong>' (force URL to be
<strong>g</strong>one)<br />
- This forces the current URL to be gone, <em>i.e.</em>, it
+ This forces the current URL to be gone - it
immediately sends back a HTTP response of 410 (GONE). Use
this flag to mark pages which no longer exist as gone.</li>
<li>'<strong><code>last|L</code></strong>'
(<strong>l</strong>ast rule)<br />
Stop the rewriting process here and don't apply any more
- rewriting rules. This corresponds to the Perl
+ rewrite rules. This corresponds to the Perl
<code>last</code> command or the <code>break</code> command
- from the C language. Use this flag to prevent the currently
+ in C. Use this flag to prevent the currently
rewritten URL from being rewritten further by following
rules. For example, use it to rewrite the root-path URL
('<code>/</code>') to a real one, <em>e.g.</em>,
@@ -1471,20 +1319,20 @@
<li>'<strong><code>next|N</code></strong>'
(<strong>n</strong>ext round)<br />
- Re-run the rewriting process (starting again with the
- first rewriting rule). Here the URL to match is again not
- the original URL but the URL from the last rewriting rule.
+ Re-run the rewriting process (starting again with the
+ first rewriting rule). This time, the URL to match is no longer
+ the original URL, but rather the URL returned by the last rewriting rule.
This corresponds to the Perl <code>next</code> command or
- the <code>continue</code> command from the C language. Use
- this flag to restart the rewriting process, <em>i.e.</em>,
+ the <code>continue</code> command in C. Use
+ this flag to restart the rewriting process -
to immediately go to the top of the loop.<br />
- <strong>But be careful not to create an infinite
+ <strong>Be careful not to create an infinite
loop!</strong></li>
<li>'<strong><code>nocase|NC</code></strong>'
(<strong>n</strong>o <strong>c</strong>ase)<br />
- This makes the <em>Pattern</em> case-insensitive,
- <em>i.e.</em>, there is no difference between 'A-Z' and
+ This makes the <em>Pattern</em> case-insensitive,
+ ignoring difference between 'A-Z' and
'a-z' when <em>Pattern</em> is matched against the current
URL.</li>
@@ -1492,12 +1340,12 @@
'<strong><code>noescape|NE</code></strong>'
(<strong>n</strong>o URI <strong>e</strong>scaping of
output)<br />
- This flag keeps mod_rewrite from applying the usual URI
+ This flag prevents mod_rewrite from applying the usual URI
escaping rules to the result of a rewrite. Ordinarily,
special characters (such as '%', '$', ';', and so on)
will be escaped into their hexcode equivalents ('%25',
'%24', and '%3B', respectively); this flag prevents this
- from being done. This allows percent symbols to appear in
+ from happening. This allows percent symbols to appear in
the output, as in
<div class="example"><p><code>
RewriteRule /foo/(.*) /bar?arg=P1\%3d$1 [R,NE]
@@ -1508,131 +1356,120 @@
</li>
<li>
- '<strong><code>nosubreq|NS</code></strong>' (used only if
- <strong>n</strong>o internal
- <strong>s</strong>ub-request)<br />
- This flag forces the rewriting engine to skip a
- rewriting rule if the current request is an internal
+ '<strong><code>nosubreq|NS</code></strong>' (
+ <strong>n</strong>ot for internal
+ <strong>s</strong>ub-requests)<br />
+ This flag forces the rewrite engine to skip a
+ rewrite rule if the current request is an internal
sub-request. For instance, sub-requests occur internally
- in Apache when <code>mod_include</code> tries to find out
+ in Apache when <code class="module"><a href="../mod/mod_include.html">mod_include</a></code> tries to find out
information about possible directory default files
(<code>index.xxx</code>). On sub-requests it is not
- always useful and even sometimes causes a failure to if
+ always useful, and can even cause errors, if
the complete set of rules are applied. Use this flag to
exclude some rules.<br />
-
-
- <p>Use the following rule for your decision: whenever you
- prefix some URLs with CGI-scripts to force them to be
- processed by the CGI-script, the chance is high that you
- will run into problems (or even overhead) on
- sub-requests. In these cases, use this flag.</p>
- </li>
+ To decide whether or not to use this rule: if you
+ prefix URLs with CGI-scripts, to force them to be
+ processed by the CGI-script, it's likely that you
+ will run into problems (or significant overhead) on
+ sub-requests. In these cases, use this flag.
+ </li>
<li>
'<strong><code>proxy|P</code></strong>' (force
<strong>p</strong>roxy)<br />
- This flag forces the substitution part to be internally
- forced as a proxy request and immediately (<em>i.e.</em>,
- rewriting rule processing stops here) put through the <a href="mod_proxy.html">proxy module</a>. You have to make
+ This flag forces the substitution part to be internally
+ sent as a proxy request and immediately (rewrite
+ processing stops here) put through the <a href="mod_proxy.html">proxy module</a>. You must make
sure that the substitution string is a valid URI
- (<em>e.g.</em>, typically starting with
+ (typically starting with
<code>http://</code><em>hostname</em>) which can be
- handled by the Apache proxy module. If not you get an
+ handled by the Apache proxy module. If not, you will get an
error from the proxy module. Use this flag to achieve a
more powerful implementation of the <a href="mod_proxy.html#proxypass">ProxyPass</a> directive,
- to map some remote stuff into the namespace of the local
- server.
+ to map remote content into the namespace of the local
+ server.
- <p>Notice: To use this functionality make sure you have
- the proxy module compiled into your Apache server
- program. If you don't know please check whether
- <code>mod_proxy.c</code> is part of the ``<code>httpd
- -l</code>'' output. If yes, this functionality is
- available to mod_rewrite. If not, then you first have to
- rebuild the ``<code>httpd</code>'' program with mod_proxy
- enabled.</p>
+ <p>Note: <code class="module"><a href="../mod/mod_proxy.html">mod_proxy</a></code> must be enabled in order
+ to use this flag.</p>
</li>
<li>
'<strong><code>passthrough|PT</code></strong>'
(<strong>p</strong>ass <strong>t</strong>hrough to next
handler)<br />
- This flag forces the rewriting engine to set the
+ This flag forces the rewrite engine to set the
<code>uri</code> field of the internal
<code>request_rec</code> structure to the value of the
<code>filename</code> field. This flag is just a hack to
- be able to post-process the output of
- <code>RewriteRule</code> directives by
+ enable post-processing of the output of
+ <code>RewriteRule</code> directives, using
<code>Alias</code>, <code>ScriptAlias</code>,
- <code>Redirect</code>, <em>etc.</em> directives from
- other URI-to-filename translators. A trivial example to
- show the semantics: If you want to rewrite
- <code>/abc</code> to <code>/def</code> via the rewriting
- engine of <code>mod_rewrite</code> and then
- <code>/def</code> to <code>/ghi</code> with
- <code>mod_alias</code>:
+ <code>Redirect</code>, and other directives from
+ various URI-to-filename translators. For example, to rewrite
+ <code>/abc</code> to <code>/def</code> using
+ <code class="module"><a href="../mod/mod_rewrite.html">mod_rewrite</a></code>, and then
+ <code>/def</code> to <code>/ghi</code> using
+ <code class="module"><a href="../mod/mod_alias.html">mod_alias</a></code>:
<div class="example"><p><code>
RewriteRule ^/abc(.*) /def$1 [PT]<br />
Alias /def /ghi
</code></p></div>
- If you omit the <code>PT</code> flag then
- <code>mod_rewrite</code> will do its job fine,
- <em>i.e.</em>, it rewrites <code>uri=/abc/...</code> to
+ If you omit the <code>PT</code> flag,
+ <code>mod_rewrite</code> will rewrite
+ <code>uri=/abc/...</code> to
<code>filename=/def/...</code> as a full API-compliant
URI-to-filename translator should do. Then
- <code>mod_alias</code> comes and tries to do a
- URI-to-filename transition which will not work.
+ <code>mod_alias</code> will try to do a
+ URI-to-filename transition, which will fail.
- <p>Note: <strong>You have to use this flag if you want to
- intermix directives of different modules which contain
+ <p>Note: <strong>You must use this flag if you want to
+ mix directives from different modules which allow
URL-to-filename translators</strong>. The typical example
- is the use of <code>mod_alias</code> and
- <code>mod_rewrite</code>..</p>
+ is the use of <code class="module"><a href="../mod/mod_alias.html">mod_alias</a></code> and
+ <code class="module"><a href="../mod/mod_rewrite.html">mod_rewrite</a></code>.</p>
</li>
<li>'<strong><code>qsappend|QSA</code></strong>'
(<strong>q</strong>uery <strong>s</strong>tring
<strong>a</strong>ppend)<br />
- This flag forces the rewriting engine to append a query
- string part in the substitution string to the existing one
+ This flag forces the rewrite engine to append a query
+ string part of the substitution string to the existing string,
instead of replacing it. Use this when you want to add more
data to the query string via a rewrite rule.</li>
<li>'<strong><code>redirect|R</code>
[=<em>code</em>]</strong>' (force <a id="redirect" name="redirect"><strong>r</strong>edirect</a>)<br />
- Prefix <em>Substitution</em> with
+ Prefix <em>Substitution</em> with
<code>http://thishost[:thisport]/</code> (which makes the
new URL a URI) to force a external redirection. If no
- <em>code</em> is given a HTTP response of 302 (MOVED
- TEMPORARILY) is used. If you want to use other response
- codes in the range 300-400 just specify them as a number
+ <em>code</em> is given, a HTTP response of 302 (MOVED
+ TEMPORARILY) will be returned. If you want to use other response
+ codes in the range 300-400, simply specify the appropriate number
or use one of the following symbolic names:
<code>temp</code> (default), <code>permanent</code>,
- <code>seeother</code>. Use it for rules which should
- canonicalize the URL and give it back to the client,
- <em>e.g.</em>, translate ``<code>/~</code>'' into
- ``<code>/u/</code>'' or always append a slash to
+ <code>seeother</code>. Use this for rules to
+ canonicalize the URL and return it to the client - to
+ translate ``<code>/~</code>'' into
+ ``<code>/u/</code>'', or to always append a slash to
<code>/u/</code><em>user</em>, etc.<br />
-
-
- <p><strong>Note:</strong> When you use this flag, make
- sure that the substitution field is a valid URL! If not,
- you are redirecting to an invalid location! And remember
- that this flag itself only prefixes the URL with
- <code>http://thishost[:thisport]/</code>, rewriting
- continues. Usually you also want to stop and do the
- redirection immediately. To stop the rewriting you also
- have to provide the 'L' flag.</p>
+ <strong>Note:</strong> When you use this flag, make
+ sure that the substitution field is a valid URL! Otherwise,
+ you will be redirecting to an invalid location. Remember
+ that this flag on its own will only prepend
+ <code>http://thishost[:thisport]/</code> to the URL, and rewriting
+ will continue. Usually, you will want to stop rewriting at this point,
+ and redirect immediately. To stop rewriting, you should add
+ the 'L' flag.
</li>
<li>'<strong><code>skip|S</code></strong>=<em>num</em>'
(<strong>s</strong>kip next rule(s))<br />
- This flag forces the rewriting engine to skip the next
- <em>num</em> rules in sequence when the current rule
+ This flag forces the rewriting engine to skip the next
+ <em>num</em> rules in sequence, if the current rule
matches. Use this to make pseudo if-then-else constructs:
The last rule of the then-clause becomes
- <code>skip=N</code> where N is the number of rules in the
+ <code>skip=N</code>, where N is the number of rules in the
else-clause. (This is <strong>not</strong> the same as the
'chain|C' flag!)</li>
@@ -1640,8 +1477,8 @@
'<strong><code>type|T</code></strong>=<em>MIME-type</em>'
(force MIME <strong>t</strong>ype)<br />
Force the MIME-type of the target file to be
- <em>MIME-type</em>. For instance, this can be used to
- setup the content-type based on some conditions.
+ <em>MIME-type</em>. This can be used to
+ set up the content-type based on some conditions.
For example, the following snippet allows <code>.php</code> files to
be <em>displayed</em> by <code>mod_php</code> if they are called with
the <code>.phps</code> extension:
@@ -1652,33 +1489,64 @@
</ul>
-<div class="note"><h3>Note</h3> Never forget that <em>Pattern</em> is
+<div class="note"><h3>Note: Enabling rewrites in per-directory context</h3>
+ To enable the rewriting engine
+ for per-directory configuration files, you need to set
+ ``<code>RewriteEngine On</code>'' in these files
+ <strong>and</strong> ``<code>Options
+ FollowSymLinks</code>'' must be enabled. If your
+ administrator has disabled override of
+ <code>FollowSymLinks</code> for a user's directory, then
+ you cannot use the rewriting engine. This restriction is
+ needed for security reasons.
+ </div>
+
+ <div class="note"><h3>Note: Pattern matching in per-directory context</h3>
+ Never forget that <em>Pattern</em> is
applied to a complete URL in per-server configuration
-files. <strong>But in per-directory configuration files, the
+files. <strong>However, in per-directory configuration files, the
per-directory prefix (which always is the same for a specific
-directory!) is automatically <em>removed</em> for the pattern matching
+directory) is automatically <em>removed</em> for the pattern matching
and automatically <em>added</em> after the substitution has been
-done.</strong> This feature is essential for many sorts of rewriting,
-because without this prefix stripping you have to match the parent
+done.</strong> This feature is essential for many sorts of rewriting -
+without this, you would always have to match the parent
directory which is not always possible.
<p>There is one exception: If a substitution string
- starts with ``<code>http://</code>'' then the directory
- prefix will <strong>not</strong> be added and an
+ starts with ``<code>http://</code>'', then the directory
+ prefix will <strong>not</strong> be added, and an
external redirect or proxy throughput (if flag
- <strong>P</strong> is used!) is forced!</p>
+ <strong>P</strong> is used) is forced!</p>
</div>
-<div class="note"><h3>Note</h3>
- To enable the rewriting engine
- for per-directory configuration files you need to set
- ``<code>RewriteEngine On</code>'' in these files
- <strong>and</strong> ``<code>Options
- FollowSymLinks</code>'' must be enabled. If your
- administrator has disabled override of
- <code>FollowSymLinks</code> for a user's directory, then
- you cannot use the rewriting engine. This restriction is
- needed for security reasons.
+
+<div class="note"><h3>Note: Substitution of Absolute URLs</h3>
+ <p>When you prefix a substitution field with
+ <code>http://thishost[:thisport]</code>,
+ <code class="module"><a href="../mod/mod_rewrite.html">mod_rewrite</a></code> will automatically strip that
+ out. This auto-reduction on URLs with an implicit external redirect
+ is most useful in combination with
+ a mapping-function which generates the
+ hostname part.</p>
+
+ <p><strong>Remember:</strong> An unconditional external
+ redirect to your own server will not work with the prefix
+ <code>http://thishost</code> because of this feature. To
+ achieve such a self-redirect, you have to use the
+ <strong>R</strong>-flag.</p>
+</div>
+
+<div class="note"><h3>Note: Query String</h3>
+ <p>The <em>Pattern</em> will not be matched against the query string.
+ Instead, you must use a <code class="directive"><a href="#rewritecond">RewriteCond</a></code> with the
+ <code>%{QUERY_STRING}</code> variable. You can, however, create
+ URLs in the substitution string, containing a query string
+ part. Simply use a question mark inside the substitution string, to
+ indicate that the following text should be re-injected into the
+ query string. When you want to erase an existing query string,
+ end the substitution string with just a question mark. To
+ combine a new query string with an old one, use the
+ <code>[QSA]</code> flag.</p>
</div>
<p>Here are all possible substitution combinations and their
@@ -1693,25 +1561,25 @@
<div class="note"><pre>
<strong>Given Rule</strong> <strong>Resulting Substitution</strong>
---------------------------------------------- ----------------------------------
-^/somepath(.*) otherpath$1 not supported, because invalid!
+^/somepath(.*) otherpath$1 invalid, not supported
-^/somepath(.*) otherpath$1 [R] not supported, because invalid!
+^/somepath(.*) otherpath$1 [R] invalid, not supported
-^/somepath(.*) otherpath$1 [P] not supported, because invalid!
+^/somepath(.*) otherpath$1 [P] invalid, not supported
---------------------------------------------- ----------------------------------
^/somepath(.*) /otherpath$1 /otherpath/pathinfo
^/somepath(.*) /otherpath$1 [R] http://thishost/otherpath/pathinfo
via external redirection
-^/somepath(.*) /otherpath$1 [P] not supported, because silly!
+^/somepath(.*) /otherpath$1 [P] doesn't make sense, not supported
---------------------------------------------- ----------------------------------
^/somepath(.*) http://thishost/otherpath$1 /otherpath/pathinfo
^/somepath(.*) http://thishost/otherpath$1 [R] http://thishost/otherpath/pathinfo
via external redirection
-^/somepath(.*) http://thishost/otherpath$1 [P] not supported, because silly!
+^/somepath(.*) http://thishost/otherpath$1 [P] doesn't make sense, not supported
---------------------------------------------- ----------------------------------
^/somepath(.*) http://otherhost/otherpath$1 http://otherhost/otherpath/pathinfo
via external redirection
@@ -1726,8 +1594,7 @@
<p><strong>Inside per-directory configuration for
<code>/somepath</code><br />
- (<em>i.e.</em>, file <code>.htaccess</code> in dir
- <code>/physical/path/to/somepath</code> containing
+ (<code>/physical/path/to/somepath/.htacccess</code>, with
<code>RewriteBase /somepath</code>)<br />
for request ``<code>GET
/somepath/localpath/pathinfo</code>'':</strong><br />
@@ -1741,21 +1608,21 @@
^localpath(.*) otherpath$1 [R] http://thishost/somepath/otherpath/pathinfo
via external redirection
-^localpath(.*) otherpath$1 [P] not supported, because silly!
+^localpath(.*) otherpath$1 [P] doesn't make sense, not supported
---------------------------------------------- ----------------------------------
^localpath(.*) /otherpath$1 /otherpath/pathinfo
^localpath(.*) /otherpath$1 [R] http://thishost/otherpath/pathinfo
via external redirection
-^localpath(.*) /otherpath$1 [P] not supported, because silly!
+^localpath(.*) /otherpath$1 [P] doesn't make sense, not supported
---------------------------------------------- ----------------------------------
^localpath(.*) http://thishost/otherpath$1 /otherpath/pathinfo
^localpath(.*) http://thishost/otherpath$1 [R] http://thishost/otherpath/pathinfo
via external redirection
-^localpath(.*) http://thishost/otherpath$1 [P] not supported, because silly!
+^localpath(.*) http://thishost/otherpath$1 [P] doesn't make sense, not supported
---------------------------------------------- ----------------------------------
^localpath(.*) http://otherhost/otherpath$1 http://otherhost/otherpath/pathinfo
via external redirection
@@ -1766,33 +1633,6 @@
^localpath(.*) http://otherhost/otherpath$1 [P] http://otherhost/otherpath/pathinfo
via internal proxy
-</pre></div>
-
- <p><strong>Example:</strong></p>
-
- <p>We want to rewrite URLs of the form </p>
-
- <p class="indent">
- <code>/</code> <em>Language</em> <code>/~</code>
- <em>Realname</em> <code>/.../</code> <em>File</em>
- </p>
-
- <p>into </p>
-
- <p class="indent">
- <code>/u/</code> <em>Username</em> <code>/.../</code>
- <em>File</em> <code>.</code> <em>Language</em>
- </p>
-
- <p>We take the rewrite mapfile from above and save it under
- <code>/path/to/file/map.txt</code>. Then we only have to
- add the following lines to the Apache server configuration
- file:</p>
-
-<div class="example"><pre>
-RewriteLog /path/to/file/rewrite.log
-RewriteMap real-to-user txt:/path/to/file/map.txt
-RewriteRule ^/([^/]+)/~([^/]+)/(.*)$ /u/${real-to-user:$2|nobody}/$3.$1
</pre></div>
</div>
Modified: httpd/httpd/branches/2.0.x/docs/manual/mod/mpm_common.html.de
URL: http://svn.apache.org/viewcvs/httpd/httpd/branches/2.0.x/docs/manual/mod/mpm_common.html.de?rev=375324&r1=375323&r2=375324&view=diff
==============================================================================
--- httpd/httpd/branches/2.0.x/docs/manual/mod/mpm_common.html.de (original)
+++ httpd/httpd/branches/2.0.x/docs/manual/mod/mpm_common.html.de Mon Feb 6 10:09:02 2006
@@ -26,6 +26,9 @@
<a href="../es/mod/mpm_common.html" hreflang="es" rel="alternate" title="Español"> es </a> |
<a href="../ja/mod/mpm_common.html" hreflang="ja" rel="alternate" title="Japanese"> ja </a></p>
</div>
+<div class="outofdate">Diese Übersetzung ist möglicherweise
+ nicht mehr aktuell. Bitte prüfen Sie die englische Version auf
+ die neuesten Änderungen.</div>
<table class="module"><tr><th><a href="module-dict.html#Description">Beschreibung:</a></th><td>Eine Sammlung von Direktiven, die in mehr als einem
Multi-Processing-Modul (MPM) implementiert sind.</td></tr>
<tr><th><a href="module-dict.html#Status">Status:</a></th><td>MPM</td></tr></table>
Modified: httpd/httpd/branches/2.0.x/docs/manual/mod/mpm_common.html.es
URL: http://svn.apache.org/viewcvs/httpd/httpd/branches/2.0.x/docs/manual/mod/mpm_common.html.es?rev=375324&r1=375323&r2=375324&view=diff
==============================================================================
--- httpd/httpd/branches/2.0.x/docs/manual/mod/mpm_common.html.es (original)
+++ httpd/httpd/branches/2.0.x/docs/manual/mod/mpm_common.html.es Mon Feb 6 10:09:02 2006
@@ -27,6 +27,10 @@
<a href="../es/mod/mpm_common.html" title="Español"> es </a> |
<a href="../ja/mod/mpm_common.html" hreflang="ja" rel="alternate" title="Japanese"> ja </a></p>
</div>
+<div class="outofdate">Esta traducción podría estar
+ obsoleta. Consulte la versión en inglés de la
+ documentación para comprobar si se han producido cambios
+ recientemente.</div>
<table class="module"><tr><th><a href="module-dict.html#Description">Descripción:</a></th><td>Es una colección de directivas que están implementadas
en más de un módulo de multiprocesamiento (MPM)</td></tr>
<tr><th><a href="module-dict.html#Status">Estado:</a></th><td>MPM</td></tr></table>
Modified: httpd/httpd/branches/2.0.x/docs/manual/mod/mpm_common.html.ja.euc-jp
URL: http://svn.apache.org/viewcvs/httpd/httpd/branches/2.0.x/docs/manual/mod/mpm_common.html.ja.euc-jp?rev=375324&r1=375323&r2=375324&view=diff
==============================================================================
--- httpd/httpd/branches/2.0.x/docs/manual/mod/mpm_common.html.ja.euc-jp [euc-jp] (original)
+++ httpd/httpd/branches/2.0.x/docs/manual/mod/mpm_common.html.ja.euc-jp [euc-jp] Mon Feb 6 10:09:02 2006
@@ -26,6 +26,8 @@
<a href="../es/mod/mpm_common.html" hreflang="es" rel="alternate" title="Español"> es </a> |
<a href="../ja/mod/mpm_common.html" title="Japanese"> ja </a></p>
</div>
+<div class="outofdate">This translation may be out of date. Check the
+ English version for recent changes.</div>
<table class="module"><tr><th><a href="module-dict.html#Description">説明:</a></th><td>二つ以上のマルチプロセッシングモジュール (MPM)
で実装されているディレクティブのコレクション</td></tr>
<tr><th><a href="module-dict.html#Status">ステータス:</a></th><td>MPM</td></tr></table>