mirror of
https://github.com/apache/httpd.git
synced 2026-01-06 09:01:14 +03:00
Change the flag list to a <dl> instead of <ul>. Seems much more readable to me.
git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/trunk@561918 13f79535-47bb-0310-9956-ffa450edef68
This commit is contained in:
Joshua Slive
@@ -1251,9 +1251,9 @@ cannot use <code>$N</code> in the substitution string!
|
||||
directive. <em>Flags</em> is a comma-separated list, surround by square
|
||||
brackets, of any of the following flags: </p>
|
||||
|
||||
<ul>
|
||||
<li>'<strong><code>chain|C</code></strong>'
|
||||
(<strong>c</strong>hained with next rule)<br />
|
||||
<dl>
|
||||
<dt>'<code>chain|C</code>'
|
||||
(chained with next rule)</dt><dd>
|
||||
This flag chains the current rule with the next rule
|
||||
(which itself can be chained with the following rule,
|
||||
and so on). This has the following effect: if a rule
|
||||
@@ -1263,21 +1263,21 @@ cannot use <code>$N</code> in the substitution string!
|
||||
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 occur!).</li>
|
||||
``<code>.www</code>'' part should not occur!).</dd>
|
||||
|
||||
<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 />
|
||||
<dt>
|
||||
'<code>cookie|CO=</code><em>NAME</em>:<em>VAL</em>:<em>domain</em>[:<em>lifetime</em>[:<em>path</em>]]'
|
||||
(set cookie)</dt><dd>
|
||||
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>
|
||||
is the lifetime of the cookie in minutes, and the optional
|
||||
<em>path</em> is the path of the cookie</li>
|
||||
<em>path</em> is the path of the cookie</dd>
|
||||
|
||||
<li>
|
||||
'<strong><code>env|E=</code></strong><em>VAR</em>:<em>VAL</em>'
|
||||
(set <strong>e</strong>nvironment variable)<br />
|
||||
<dt>
|
||||
'<code>env|E=</code><em>VAR</em>:<em>VAL</em>'
|
||||
(set environment variable)</dt><dd>
|
||||
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
|
||||
@@ -1288,35 +1288,35 @@ cannot use <code>$N</code> in the substitution string!
|
||||
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>
|
||||
information from URLs, while maintaining a record of that information.</dd>
|
||||
|
||||
<li>'<strong><code>forbidden|F</code></strong>' (force URL
|
||||
to be <strong>f</strong>orbidden)<br />
|
||||
<dt>'<code>forbidden|F</code>' (force URL
|
||||
to be forbidden)</dt><dd>
|
||||
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>
|
||||
URLs.</dd>
|
||||
|
||||
<li>'<strong><code>gone|G</code></strong>' (force URL to be
|
||||
<strong>g</strong>one)<br />
|
||||
<dt>'<code>gone|G</code>' (force URL to be
|
||||
gone)</dt><dd>
|
||||
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>
|
||||
this flag to mark pages which no longer exist as gone.</dd>
|
||||
|
||||
<li>
|
||||
'<strong><code>handler|H</code></strong>=<em>Content-handler</em>'
|
||||
(force Content <strong>h</strong>andler)<br />
|
||||
<dt>
|
||||
'<code>handler|H</code>=<em>Content-handler</em>'
|
||||
(force Content handler)</dt><dd>
|
||||
Force the Content-handler of the target file to be
|
||||
<em>Content-handler</em>. For instance, this can be used to
|
||||
simulate the <code class="module"><a href="../mod/mod_alias.html">mod_alias</a></code> directive
|
||||
<code class="directive"><a href="../mod/mod_alias.html#scriptalias">ScriptAlias</a></code>,
|
||||
which internally forces all files
|
||||
inside the mapped directory to have a handler of
|
||||
``<code>cgi-script</code>''.</li>
|
||||
``<code>cgi-script</code>''.</dd>
|
||||
|
||||
<li>'<strong><code>last|L</code></strong>'
|
||||
(<strong>l</strong>ast rule)<br /> Stop the rewriting process
|
||||
<dt>'<code>last|L</code>'
|
||||
(last rule)</dt><dd> Stop the rewriting process
|
||||
here and don't apply any more rewrite rules. This corresponds
|
||||
to the Perl <code>last</code> command or the
|
||||
<code>break</code> command in C. Use this flag to prevent the
|
||||
@@ -1326,31 +1326,31 @@ cannot use <code>$N</code> in the substitution string!
|
||||
redirect (which frequently occurs when rewriting in a
|
||||
per-directory context), this will reinject the request and
|
||||
will cause processing to be repeated starting from the first
|
||||
<code class="directive">RewriteRule</code>.</li>
|
||||
<code class="directive">RewriteRule</code>.</dd>
|
||||
|
||||
<li>'<strong><code>next|N</code></strong>'
|
||||
(<strong>n</strong>ext round)<br />
|
||||
<dt>'<code>next|N</code>'
|
||||
(next round)</dt><dd>
|
||||
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 in C. Use
|
||||
this flag to restart the rewriting process -
|
||||
to immediately go to the top of the loop.<br />
|
||||
to immediately go to the top of the loop.
|
||||
<strong>Be careful not to create an infinite
|
||||
loop!</strong></li>
|
||||
loop!</strong></dd>
|
||||
|
||||
<li>'<strong><code>nocase|NC</code></strong>'
|
||||
(<strong>n</strong>o <strong>c</strong>ase)<br />
|
||||
<dt>'<code>nocase|NC</code>'
|
||||
(no case)</dt><dd>
|
||||
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>
|
||||
URL.</dd>
|
||||
|
||||
<li>
|
||||
'<strong><code>noescape|NE</code></strong>'
|
||||
(<strong>n</strong>o URI <strong>e</strong>scaping of
|
||||
output)<br />
|
||||
<dt>
|
||||
'<code>noescape|NE</code>'
|
||||
(no URI escaping of
|
||||
output)</dt><dd>
|
||||
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)
|
||||
@@ -1363,13 +1363,13 @@ cannot use <code>$N</code> in the substitution string!
|
||||
</code></p></div>
|
||||
which would turn '<code>/foo/zed</code>' into a safe
|
||||
request for '<code>/bar?arg=P1=zed</code>'.
|
||||
</li>
|
||||
</dd>
|
||||
|
||||
<li>
|
||||
'<strong><code>nosubreq|NS</code></strong>'
|
||||
(<strong>n</strong>ot for internal
|
||||
<strong>s</strong>ub-requests)<br />
|
||||
This flag forces the rewriting engine to skip a
|
||||
<dt>
|
||||
'<code>nosubreq|NS</code>'
|
||||
(not for internal
|
||||
sub-requests)</dt><dd>
|
||||
<p>This flag forces the rewriting engine to skip a
|
||||
rewriting rule if the current request is an internal
|
||||
sub-request. For instance, sub-requests occur internally
|
||||
in Apache when <code class="module"><a href="../mod/mod_include.html">mod_include</a></code> tries to find out
|
||||
@@ -1377,17 +1377,17 @@ cannot use <code>$N</code> in the substitution string!
|
||||
(<code>index.xxx</code> files). On sub-requests it is not
|
||||
always useful, and can even cause errors, if
|
||||
the complete set of rules are applied. Use this flag to
|
||||
exclude some rules.<br />
|
||||
To decide whether or not to use this rule: if you
|
||||
exclude some rules.</p>
|
||||
<p>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>
|
||||
sub-requests. In these cases, use this flag.</p>
|
||||
</dd>
|
||||
|
||||
<li>
|
||||
'<strong><code>proxy|P</code></strong>' (force
|
||||
<strong>p</strong>roxy)<br />
|
||||
<dt>
|
||||
'<code>proxy|P</code>' (force
|
||||
proxy)</dt><dd>
|
||||
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
|
||||
@@ -1402,12 +1402,12 @@ cannot use <code>$N</code> in the substitution string!
|
||||
|
||||
<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>
|
||||
</dd>
|
||||
|
||||
<li>
|
||||
'<strong><code>passthrough|PT</code></strong>'
|
||||
(<strong>p</strong>ass <strong>t</strong>hrough to next
|
||||
handler)<br />
|
||||
<dt>
|
||||
'<code>passthrough|PT</code>'
|
||||
(pass through to next
|
||||
handler)</dt><dd>
|
||||
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
|
||||
@@ -1442,59 +1442,58 @@ cannot use <code>$N</code> in the substitution string!
|
||||
<p>The <code>PT</code> flag implies the <code>L</code> flag:
|
||||
rewriting will be stopped in order to pass the request to
|
||||
the next phase of processing.</p>
|
||||
</li>
|
||||
</dd>
|
||||
|
||||
<li>'<strong><code>qsappend|QSA</code></strong>'
|
||||
(<strong>q</strong>uery <strong>s</strong>tring
|
||||
<strong>a</strong>ppend)<br />
|
||||
<dt>'<code>qsappend|QSA</code>'
|
||||
(query string
|
||||
append)</dt><dd>
|
||||
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>
|
||||
data to the query string via a rewrite rule.</dd>
|
||||
|
||||
<li>'<strong><code>redirect|R</code>
|
||||
[=<em>code</em>]</strong>' (force <a id="redirect" name="redirect"><strong>r</strong>edirect</a>)<br />
|
||||
<p>Prefix <em>Substitution</em> with
|
||||
<dt>'<code>redirect|R</code>
|
||||
[=<em>code</em>]' (force <a id="redirect" name="redirect">redirect</a>)</dt><dd>
|
||||
<p>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) will be returned. If you want to use other response
|
||||
codes, simply specify the appropriate number
|
||||
or use one of the following symbolic names:
|
||||
<code>temp</code> (default), <code>permanent</code>,
|
||||
<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 />
|
||||
<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.</p>
|
||||
TEMPORARILY) will be returned. If you want to use other
|
||||
response codes, simply specify the appropriate number or use
|
||||
one of the following symbolic names: <code>temp</code>
|
||||
(default), <code>permanent</code>,
|
||||
<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 />
|
||||
<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.</p>
|
||||
<p>While this is typically used for redirects, any valid status
|
||||
code can be given here. If the status code is outside the redirect
|
||||
range (300-399), then the <em>Substitution</em> string is dropped
|
||||
and rewriting is stopped as if the <code>L</code> flag was
|
||||
used.</p>
|
||||
</li>
|
||||
</dd>
|
||||
|
||||
<li>'<strong><code>skip|S</code></strong>=<em>num</em>'
|
||||
(<strong>s</strong>kip next rule(s))<br />
|
||||
<dt>'<code>skip|S</code>=<em>num</em>'
|
||||
(skip next rule(s))</dt><dd>
|
||||
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
|
||||
else-clause. (This is <strong>not</strong> the same as the
|
||||
'chain|C' flag!)</li>
|
||||
'chain|C' flag!)</dd>
|
||||
|
||||
<li>
|
||||
'<strong><code>type|T</code></strong>=<em>MIME-type</em>'
|
||||
(force MIME <strong>t</strong>ype)<br />
|
||||
<dt>
|
||||
'<code>type|T</code>=<em>MIME-type</em>'
|
||||
(force MIME type)</dt><dd>
|
||||
Force the <a class="glossarylink" href="../glossary.html#mime-type" title="see glossary">MIME-type</a> of the target file to be
|
||||
<em>MIME-type</em>. This can be used to
|
||||
set up the content-type based on some conditions.
|
||||
@@ -1504,8 +1503,8 @@ cannot use <code>$N</code> in the substitution string!
|
||||
<div class="example"><p><code>
|
||||
RewriteRule ^(.+\.php)s$ $1 [T=application/x-httpd-php-source]
|
||||
</code></p></div>
|
||||
</li>
|
||||
</ul>
|
||||
</dd>
|
||||
</dl>
|
||||
|
||||
<div class="note"><h3>Per-directory Rewrites</h3>
|
||||
|
||||
|
||||
@@ -1268,9 +1268,9 @@ cannot use <code>$N</code> in the substitution string!
|
||||
directive. <em>Flags</em> is a comma-separated list, surround by square
|
||||
brackets, of any of the following flags: </p>
|
||||
|
||||
<ul>
|
||||
<li>'<strong><code>chain|C</code></strong>'
|
||||
(<strong>c</strong>hained with next rule)<br />
|
||||
<dl>
|
||||
<dt>'<code>chain|C</code>'
|
||||
(chained with next rule)</dt><dd>
|
||||
This flag chains the current rule with the next rule
|
||||
(which itself can be chained with the following rule,
|
||||
and so on). This has the following effect: if a rule
|
||||
@@ -1280,21 +1280,21 @@ cannot use <code>$N</code> in the substitution string!
|
||||
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 occur!).</li>
|
||||
``<code>.www</code>'' part should not occur!).</dd>
|
||||
|
||||
<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 />
|
||||
<dt>
|
||||
'<code>cookie|CO=</code><em>NAME</em>:<em>VAL</em>:<em>domain</em>[:<em>lifetime</em>[:<em>path</em>]]'
|
||||
(set cookie)</dt><dd>
|
||||
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>
|
||||
is the lifetime of the cookie in minutes, and the optional
|
||||
<em>path</em> is the path of the cookie</li>
|
||||
<em>path</em> is the path of the cookie</dd>
|
||||
|
||||
<li>
|
||||
'<strong><code>env|E=</code></strong><em>VAR</em>:<em>VAL</em>'
|
||||
(set <strong>e</strong>nvironment variable)<br />
|
||||
<dt>
|
||||
'<code>env|E=</code><em>VAR</em>:<em>VAL</em>'
|
||||
(set environment variable)</dt><dd>
|
||||
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
|
||||
@@ -1305,35 +1305,35 @@ cannot use <code>$N</code> in the substitution string!
|
||||
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>
|
||||
information from URLs, while maintaining a record of that information.</dd>
|
||||
|
||||
<li>'<strong><code>forbidden|F</code></strong>' (force URL
|
||||
to be <strong>f</strong>orbidden)<br />
|
||||
<dt>'<code>forbidden|F</code>' (force URL
|
||||
to be forbidden)</dt><dd>
|
||||
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>
|
||||
URLs.</dd>
|
||||
|
||||
<li>'<strong><code>gone|G</code></strong>' (force URL to be
|
||||
<strong>g</strong>one)<br />
|
||||
<dt>'<code>gone|G</code>' (force URL to be
|
||||
gone)</dt><dd>
|
||||
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>
|
||||
this flag to mark pages which no longer exist as gone.</dd>
|
||||
|
||||
<li>
|
||||
'<strong><code>handler|H</code></strong>=<em>Content-handler</em>'
|
||||
(force Content <strong>h</strong>andler)<br />
|
||||
<dt>
|
||||
'<code>handler|H</code>=<em>Content-handler</em>'
|
||||
(force Content handler)</dt><dd>
|
||||
Force the Content-handler of the target file to be
|
||||
<em>Content-handler</em>. For instance, this can be used to
|
||||
simulate the <module>mod_alias</module> directive
|
||||
<directive module="mod_alias">ScriptAlias</directive>,
|
||||
which internally forces all files
|
||||
inside the mapped directory to have a handler of
|
||||
``<code>cgi-script</code>''.</li>
|
||||
``<code>cgi-script</code>''.</dd>
|
||||
|
||||
<li>'<strong><code>last|L</code></strong>'
|
||||
(<strong>l</strong>ast rule)<br /> Stop the rewriting process
|
||||
<dt>'<code>last|L</code>'
|
||||
(last rule)</dt><dd> Stop the rewriting process
|
||||
here and don't apply any more rewrite rules. This corresponds
|
||||
to the Perl <code>last</code> command or the
|
||||
<code>break</code> command in C. Use this flag to prevent the
|
||||
@@ -1343,31 +1343,31 @@ cannot use <code>$N</code> in the substitution string!
|
||||
redirect (which frequently occurs when rewriting in a
|
||||
per-directory context), this will reinject the request and
|
||||
will cause processing to be repeated starting from the first
|
||||
<directive>RewriteRule</directive>.</li>
|
||||
<directive>RewriteRule</directive>.</dd>
|
||||
|
||||
<li>'<strong><code>next|N</code></strong>'
|
||||
(<strong>n</strong>ext round)<br />
|
||||
<dt>'<code>next|N</code>'
|
||||
(next round)</dt><dd>
|
||||
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 in C. Use
|
||||
this flag to restart the rewriting process -
|
||||
to immediately go to the top of the loop.<br />
|
||||
to immediately go to the top of the loop.
|
||||
<strong>Be careful not to create an infinite
|
||||
loop!</strong></li>
|
||||
loop!</strong></dd>
|
||||
|
||||
<li>'<strong><code>nocase|NC</code></strong>'
|
||||
(<strong>n</strong>o <strong>c</strong>ase)<br />
|
||||
<dt>'<code>nocase|NC</code>'
|
||||
(no case)</dt><dd>
|
||||
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>
|
||||
URL.</dd>
|
||||
|
||||
<li>
|
||||
'<strong><code>noescape|NE</code></strong>'
|
||||
(<strong>n</strong>o URI <strong>e</strong>scaping of
|
||||
output)<br />
|
||||
<dt>
|
||||
'<code>noescape|NE</code>'
|
||||
(no URI escaping of
|
||||
output)</dt><dd>
|
||||
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)
|
||||
@@ -1380,13 +1380,13 @@ cannot use <code>$N</code> in the substitution string!
|
||||
</example>
|
||||
which would turn '<code>/foo/zed</code>' into a safe
|
||||
request for '<code>/bar?arg=P1=zed</code>'.
|
||||
</li>
|
||||
</dd>
|
||||
|
||||
<li>
|
||||
'<strong><code>nosubreq|NS</code></strong>'
|
||||
(<strong>n</strong>ot for internal
|
||||
<strong>s</strong>ub-requests)<br />
|
||||
This flag forces the rewriting engine to skip a
|
||||
<dt>
|
||||
'<code>nosubreq|NS</code>'
|
||||
(not for internal
|
||||
sub-requests)</dt><dd>
|
||||
<p>This flag forces the rewriting engine to skip a
|
||||
rewriting rule if the current request is an internal
|
||||
sub-request. For instance, sub-requests occur internally
|
||||
in Apache when <module>mod_include</module> tries to find out
|
||||
@@ -1394,17 +1394,17 @@ cannot use <code>$N</code> in the substitution string!
|
||||
(<code>index.xxx</code> files). On sub-requests it is not
|
||||
always useful, and can even cause errors, if
|
||||
the complete set of rules are applied. Use this flag to
|
||||
exclude some rules.<br />
|
||||
To decide whether or not to use this rule: if you
|
||||
exclude some rules.</p>
|
||||
<p>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>
|
||||
sub-requests. In these cases, use this flag.</p>
|
||||
</dd>
|
||||
|
||||
<li>
|
||||
'<strong><code>proxy|P</code></strong>' (force
|
||||
<strong>p</strong>roxy)<br />
|
||||
<dt>
|
||||
'<code>proxy|P</code>' (force
|
||||
proxy)</dt><dd>
|
||||
This flag forces the substitution part to be internally
|
||||
sent as a proxy request and immediately (rewrite
|
||||
processing stops here) put through the <a
|
||||
@@ -1421,12 +1421,12 @@ cannot use <code>$N</code> in the substitution string!
|
||||
|
||||
<p>Note: <module>mod_proxy</module> must be enabled in order
|
||||
to use this flag.</p>
|
||||
</li>
|
||||
</dd>
|
||||
|
||||
<li>
|
||||
'<strong><code>passthrough|PT</code></strong>'
|
||||
(<strong>p</strong>ass <strong>t</strong>hrough to next
|
||||
handler)<br />
|
||||
<dt>
|
||||
'<code>passthrough|PT</code>'
|
||||
(pass through to next
|
||||
handler)</dt><dd>
|
||||
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
|
||||
@@ -1461,60 +1461,59 @@ cannot use <code>$N</code> in the substitution string!
|
||||
<p>The <code>PT</code> flag implies the <code>L</code> flag:
|
||||
rewriting will be stopped in order to pass the request to
|
||||
the next phase of processing.</p>
|
||||
</li>
|
||||
</dd>
|
||||
|
||||
<li>'<strong><code>qsappend|QSA</code></strong>'
|
||||
(<strong>q</strong>uery <strong>s</strong>tring
|
||||
<strong>a</strong>ppend)<br />
|
||||
<dt>'<code>qsappend|QSA</code>'
|
||||
(query string
|
||||
append)</dt><dd>
|
||||
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>
|
||||
data to the query string via a rewrite rule.</dd>
|
||||
|
||||
<li>'<strong><code>redirect|R</code>
|
||||
[=<em>code</em>]</strong>' (force <a id="redirect"
|
||||
name="redirect"><strong>r</strong>edirect</a>)<br />
|
||||
<p>Prefix <em>Substitution</em> with
|
||||
<dt>'<code>redirect|R</code>
|
||||
[=<em>code</em>]' (force <a id="redirect"
|
||||
name="redirect">redirect</a>)</dt><dd>
|
||||
<p>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) will be returned. If you want to use other response
|
||||
codes, simply specify the appropriate number
|
||||
or use one of the following symbolic names:
|
||||
<code>temp</code> (default), <code>permanent</code>,
|
||||
<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 />
|
||||
<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.</p>
|
||||
TEMPORARILY) will be returned. If you want to use other
|
||||
response codes, simply specify the appropriate number or use
|
||||
one of the following symbolic names: <code>temp</code>
|
||||
(default), <code>permanent</code>,
|
||||
<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 />
|
||||
<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.</p>
|
||||
<p>While this is typically used for redirects, any valid status
|
||||
code can be given here. If the status code is outside the redirect
|
||||
range (300-399), then the <em>Substitution</em> string is dropped
|
||||
and rewriting is stopped as if the <code>L</code> flag was
|
||||
used.</p>
|
||||
</li>
|
||||
</dd>
|
||||
|
||||
<li>'<strong><code>skip|S</code></strong>=<em>num</em>'
|
||||
(<strong>s</strong>kip next rule(s))<br />
|
||||
<dt>'<code>skip|S</code>=<em>num</em>'
|
||||
(skip next rule(s))</dt><dd>
|
||||
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
|
||||
else-clause. (This is <strong>not</strong> the same as the
|
||||
'chain|C' flag!)</li>
|
||||
'chain|C' flag!)</dd>
|
||||
|
||||
<li>
|
||||
'<strong><code>type|T</code></strong>=<em>MIME-type</em>'
|
||||
(force MIME <strong>t</strong>ype)<br />
|
||||
<dt>
|
||||
'<code>type|T</code>=<em>MIME-type</em>'
|
||||
(force MIME type)</dt><dd>
|
||||
Force the <glossary>MIME-type</glossary> of the target file to be
|
||||
<em>MIME-type</em>. This can be used to
|
||||
set up the content-type based on some conditions.
|
||||
@@ -1524,8 +1523,8 @@ cannot use <code>$N</code> in the substitution string!
|
||||
<example>
|
||||
RewriteRule ^(.+\.php)s$ $1 [T=application/x-httpd-php-source]
|
||||
</example>
|
||||
</li>
|
||||
</ul>
|
||||
</dd>
|
||||
</dl>
|
||||
|
||||
<note><title>Per-directory Rewrites</title>
|
||||
|
||||
|
||||
Reference in New Issue
Block a user