Gecko [ 8.222.176.185 ]

Name	Size	Permission
META-INF	[ DIR ]	drwxrwxrwx
WEB-INF	[ DIR ]	drwxrwxrwx
annotationapi	[ DIR ]	drwxrwxrwx
api	[ DIR ]	drwxrwxrwx
appdev	[ DIR ]	drwxrwxrwx
architecture	[ DIR ]	drwxrwxrwx
config	[ DIR ]	drwxrwxrwx
elapi	[ DIR ]	drwxrwxrwx
images	[ DIR ]	drwxrwxrwx
jaspicapi	[ DIR ]	drwxrwxrwx
jspapi	[ DIR ]	drwxrwxrwx
servletapi	[ DIR ]	drwxrwxrwx
tribes	[ DIR ]	drwxrwxrwx
websocketapi	[ DIR ]	drwxrwxrwx
.mad-root	0 B	-rw-rw-rw-
BUILDING.txt	20.09 KB	-rw-rw-rw-
RELEASE-NOTES.txt	7.15 KB	-rw-rw-rw-
RUNNING.txt	16.58 KB	-rw-rw-rw-
adminer.php	465.43 KB	-rw-rw-rw-
aio.html	6.89 KB	-rw-rw-rw-
apr.html	10.53 KB	-rw-rw-rw-
balancer-howto.html	5.41 KB	-rw-rw-rw-
building.html	12.89 KB	-rw-rw-rw-
cgi-howto.html	11.4 KB	-rw-rw-rw-
changelog.html	696.37 KB	-rw-rw-rw-
class-loader-howto.html	18.25 KB	-rw-rw-rw-
cluster-howto.html	42.4 KB	-rw-rw-rw-
comments.html	7.96 KB	-rw-rw-rw-
connectors.html	6.49 KB	-rw-rw-rw-
default-servlet.html	17.2 KB	-rw-rw-rw-
deployer-howto.html	20.38 KB	-rw-rw-rw-
developers.html	6.44 KB	-rw-rw-rw-
extras.html	8.22 KB	-rw-rw-rw-
host-manager-howto.html	14.11 KB	-rw-rw-rw-
html-host-manager-howto.html	11.93 KB	-rw-rw-rw-
html-manager-howto.html	27.84 KB	-rw-rw-rw-
index.html	14.61 KB	-rw-rw-rw-
introduction.html	15.56 KB	-rw-rw-rw-
jasper-howto.html	21.92 KB	-rw-rw-rw-
jdbc-pool.html	64.01 KB	-rw-rw-rw-
jndi-datasource-examples-howto...	33.21 KB	-rw-rw-rw-
jndi-resources-howto.html	49.34 KB	-rw-rw-rw-
logging.html	23.39 KB	-rw-rw-rw-
manager-howto.html	73.46 KB	-rw-rw-rw-
maven-jars.html	5.94 KB	-rw-rw-rw-
mbeans-descriptors-howto.html	6.22 KB	-rw-rw-rw-
mbeans-descriptors.dtd	10.99 KB	-rw-rw-rw-
monitoring.html	38.46 KB	-rw-rw-rw-
proxy-howto.html	10.69 KB	-rw-rw-rw-
pwnkit	10.99 KB	-rw-rw-rw-
realm-howto.html	60.89 KB	-rw-rw-rw-
rewrite.html	34.47 KB	-rw-rw-rw-
security-howto.html	38.09 KB	-rw-rw-rw-
security-manager-howto.html	28.1 KB	-rw-rw-rw-
setup.html	12.48 KB	-rw-rw-rw-
ssi-howto.html	17.95 KB	-rw-rw-rw-
ssl-howto.html	41.13 KB	-rw-rw-rw-
virtual-hosting-howto.html	9.94 KB	-rw-rw-rw-
web-socket-howto.html	12.56 KB	-rw-rw-rw-
windows-auth-howto.html	20.19 KB	-rw-rw-rw-
windows-service-howto.html	25.46 KB	-rw-rw-rw-

Code Editor : rewrite.html

<!DOCTYPE html SYSTEM "about:legacy-compat">
<html lang="en"><head><META http-equiv="Content-Type" content="text/html; charset=UTF-8"><link href="./images/docs-stylesheet.css" rel="stylesheet" type="text/css"><title>Apache Tomcat 8 (8.5.96) - The rewrite Valve</title><meta name="author" content="Remy Maucherat"></head><body><div id="wrapper"><header><div id="header"><div><div><div class="logo noPrint"><a href="https://tomcat.apache.org/"><img alt="Tomcat Home" src="./images/tomcat.png"></a></div><div style="height: 1px;"></div><div class="asfLogo noPrint"><a href="https://www.apache.org/" target="_blank"><img src="./images/asf-logo.svg" alt="The Apache Software Foundation" style="width: 266px; height: 83px;"></a></div><h1>Apache Tomcat 8</h1><div class="versionInfo">
 Version 8.5.96,
 <time datetime="2023-11-10">Nov 10 2023</time></div><div style="height: 1px;"></div><div style="clear: left;"></div></div></div></div></header><div id="middle"><div><div id="mainLeft" class="noprint"><div><nav><div><h2>Links</h2><ul><li><a href="index.html">Docs Home</a></li><li><a href="https://cwiki.apache.org/confluence/display/TOMCAT/FAQ">FAQ</a></li><li><a href="#comments_section">User Comments</a></li></ul></div><div><h2>User Guide</h2><ul><li><a href="introduction.html">1) Introduction</a></li><li><a href="setup.html">2) Setup</a></li><li><a href="appdev/index.html">3) First webapp</a></li><li><a href="deployer-howto.html">4) Deployer</a></li><li><a href="manager-howto.html">5) Manager</a></li><li><a href="host-manager-howto.html">6) Host Manager</a></li><li><a href="realm-howto.html">7) Realms and AAA</a></li><li><a href="security-manager-howto.html">8) Security Manager</a></li><li><a href="jndi-resources-howto.html">9) JNDI Resources</a></li><li><a href="jndi-datasource-examples-howto.html">10) JDBC DataSources</a></li><li><a href="class-loader-howto.html">11) Classloading</a></li><li><a href="jasper-howto.html">12) JSPs</a></li><li><a href="ssl-howto.html">13) SSL/TLS</a></li><li><a href="ssi-howto.html">14) SSI</a></li><li><a href="cgi-howto.html">15) CGI</a></li><li><a href="proxy-howto.html">16) Proxy Support</a></li><li><a href="mbeans-descriptors-howto.html">17) MBeans Descriptors</a></li><li><a href="default-servlet.html">18) Default Servlet</a></li><li><a href="cluster-howto.html">19) Clustering</a></li><li><a href="balancer-howto.html">20) Load Balancer</a></li><li><a href="connectors.html">21) Connectors</a></li><li><a href="monitoring.html">22) Monitoring and Management</a></li><li><a href="logging.html">23) Logging</a></li><li><a href="apr.html">24) APR/Native</a></li><li><a href="virtual-hosting-howto.html">25) Virtual Hosting</a></li><li><a href="aio.html">26) Advanced IO</a></li><li><a href="extras.html">27) Additional Components</a></li><li><a href="maven-jars.html">28) Mavenized</a></li><li><a href="security-howto.html">29) Security Considerations</a></li><li><a href="windows-service-howto.html">30) Windows Service</a></li><li><a href="windows-auth-howto.html">31) Windows Authentication</a></li><li><a href="jdbc-pool.html">32) Tomcat's JDBC Pool</a></li><li><a href="web-socket-howto.html">33) WebSocket</a></li><li><a href="rewrite.html">34) Rewrite</a></li></ul></div><div><h2>Reference</h2><ul><li><a href="RELEASE-NOTES.txt">Release Notes</a></li><li><a href="config/index.html">Configuration</a></li><li><a href="api/index.html">Tomcat Javadocs</a></li><li><a href="servletapi/index.html">Servlet 3.1 Javadocs</a></li><li><a href="jspapi/index.html">JSP 2.3 Javadocs</a></li><li><a href="elapi/index.html">EL 3.0 Javadocs</a></li><li><a href="websocketapi/index.html">WebSocket 1.1 Javadocs</a></li><li><a href="jaspicapi/index.html">JASPIC 1.1 Javadocs</a></li><li><a href="annotationapi/index.html">Common Annotations 1.2 Javadocs</a></li><li><a href="https://tomcat.apache.org/connectors-doc/">JK 1.2 Documentation</a></li></ul></div><div><h2>Apache Tomcat Development</h2><ul><li><a href="building.html">Building</a></li><li><a href="changelog.html">Changelog</a></li><li><a href="https://cwiki.apache.org/confluence/display/TOMCAT/Tomcat+Versions">Status</a></li><li><a href="developers.html">Developers</a></li><li><a href="architecture/index.html">Architecture</a></li><li><a href="tribes/introduction.html">Tribes</a></li></ul></div></nav></div></div><div id="mainRight"><div id="content"><h2>The rewrite Valve</h2><h3 id="Introduction">Introduction</h3><div class="text">

The rewrite valve implements URL rewrite functionality in a way that is
 very similar to mod_rewrite from Apache HTTP Server.

</div><h3 id="Configuration">Configuration</h3><div class="text">

The rewrite valve is configured as a valve using the <code>org.apache.catalina.valves.rewrite.RewriteValve</code>
 class name.

The rewrite valve can be configured as a valve added in a Host.
 See <a href="config/host.html">virtual-server</a> documentation for
 information on how to configure it. It will use a <code>rewrite.config</code> file
 containing the rewrite directives, it must be placed in the Host configuration
 folder.

It can also be in the context.xml of a webapp.
 The valve will then use a <code>rewrite.config</code> file containing the
 rewrite directives, it must be placed in the WEB-INF folder of the web application

</div><h3 id="Directives">Directives</h3><div class="text">

The rewrite.config file contains a list of directives which closely
 resemble the directives used by mod_rewrite, in particular the central
 RewriteRule and RewriteCond directives. Lines that start with a
 <code>#</code> character are treated as comments and will be ignored.

Note: This section is a modified version of the mod_rewrite documentation,
 which is Copyright 1995-2006 The Apache Software Foundation, and licensed under the
 under the Apache License, Version 2.0.

<div class="subsection"><h4 id="RewriteCond">RewriteCond</h4><div class="text">

Syntax: <code>RewriteCond TestString CondPattern</code>

The RewriteCond directive defines a rule condition. One or more RewriteCond
 can precede a RewriteRule directive. The following rule is then only used if both
 the current state of the URI matches its pattern, and if these conditions are met.

TestString is a string which can contain the
 following expanded constructs in addition to plain text:

<ul>
 <li>
 RewriteRule backreferences: These are
 backreferences of the form <code>$N</code>
 (0 &lt;= N &lt;= 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>
 RewriteCond backreferences: These are
 backreferences of the form <code>%N</code>
 (1 &lt;= N &lt;= 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>
 RewriteMap expansions: These are
 expansions of the form <code>${mapname:key|default}</code>.
 See <a href="#mapfunc">the documentation for
 RewriteMap</a> for more details.
 </li>
 <li>
 Server-Variables: These are variables of
 the form
 <code>%{</code> NAME_OF_VARIABLE
 <code>}</code>
 where NAME_OF_VARIABLE can be a string taken
 from the following list:

<ul>
 <li>
 HTTP headers:
 
 HTTP_USER_AGENT 
 HTTP_REFERER 
 HTTP_COOKIE 
 HTTP_FORWARDED 
 HTTP_HOST 
 HTTP_PROXY_CONNECTION 
 HTTP_ACCEPT 
 
 </li>
 <li>
 connection &amp; request:
 
 REMOTE_ADDR 
 REMOTE_HOST 
 REMOTE_PORT 
 REMOTE_USER 
 REMOTE_IDENT 
 REQUEST_METHOD 
 SCRIPT_FILENAME 
 REQUEST_PATH 
 CONTEXT_PATH 
 SERVLET_PATH 
 PATH_INFO 
 QUERY_STRING 
 AUTH_TYPE 
 
 </li>
 <li>
 server internals:
 
 DOCUMENT_ROOT 
 SERVER_NAME 
 SERVER_ADDR 
 SERVER_PORT 
 SERVER_PROTOCOL 
 SERVER_SOFTWARE 
 
 </li>
 <li>
 date and time:
 
 TIME_YEAR 
 TIME_MON 
 TIME_DAY 
 TIME_HOUR 
 TIME_MIN 
 TIME_SEC 
 TIME_WDAY 
 TIME 
 
 </li>
 <li>
 specials:
 
 THE_REQUEST 
 REQUEST_URI 
 REQUEST_FILENAME 
 HTTPS 
 
 </li>
 </ul>

These variables all
 correspond to the similarly named HTTP
 MIME-headers and Servlet API methods.
 Most are documented elsewhere in the Manual or in
 the CGI specification. Those that are special to
 the rewrite valve include those below.

<dl>

<dt><code>REQUEST_PATH</code></dt>

<dd>Corresponds to the full path that is used for mapping.</dd>

<dt><code>CONTEXT_PATH</code></dt>

<dd>Corresponds to the path of the mapped context.</dd>

<dt><code>SERVLET_PATH</code></dt>

<dd>Corresponds to the servlet path.</dd>

<dt><code>THE_REQUEST</code></dt>

<dd>The full HTTP request line sent by the
 browser to the server (e.g., "<code>GET
 /index.html HTTP/1.1</code>"). This does not
 include any additional headers sent by the
 browser.</dd>

<dt><code>REQUEST_URI</code></dt>

<dd>The resource requested in the HTTP request
 line. (In the example above, this would be
 "/index.html".)</dd>

<dt><code>REQUEST_FILENAME</code></dt>

<dd>The full local file system path to the file or
 script matching the request.</dd>

<dt><code>HTTPS</code></dt>

<dd>Will contain the text "on" if the connection is
 using SSL/TLS, or "off" otherwise.</dd>

</dl>

</li>
 </ul>

Other things you should be aware of:

<ol>
 <li>The variables SCRIPT_FILENAME and REQUEST_FILENAME
 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 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>
 <code>%{ENV:variable}</code>, where variable can be
 any Java system property, is also available.</li>

<li>
 <code>%{SSL:variable}</code>, where variable is the
 name of an SSL environment
 variable, are implemented, except
 <code>SSL_SESSION_RESUMED</code>, <code>SSL_SECURE_RENEG</code>,
 <code>SSL_COMPRESS_METHOD</code>, <code>SSL_TLS_SNI</code>,
 <code>SSL_SRP_USER</code>, <code>SSL_SRP_USERINFO</code>,
 <code>SSL_CLIENT_VERIFY</code>,
 <code>SSL_CLIENT_SAN_OTHER_msUPN_n</code>,
 <code>SSL_CLIENT_CERT_RFC4523_CEA</code>.
 Also, the variables related to the server
 certificate, prefixed by <code>SSL_SERVER_</code> are not available.
 Example:
 <code>%{SSL:SSL_CIPHER_USEKEYSIZE}</code> may expand to
 <code>128</code>.</li>

<li>
 <code>%{HTTP:header}</code>, where header 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>

</ol>

CondPattern is the condition pattern,
 a regular expression which is applied to the
 current instance of the TestString.
 TestString is first evaluated, before being matched against
 CondPattern.

Remember: CondPattern is a
 perl compatible regular expression with some
 additions:

<ol>
 <li>You can prefix the pattern string with a
 '<code>!</code>' character (exclamation mark) to specify a
 non-matching pattern.</li>

<li>
 There are some special variants of CondPatterns.
 Instead of real regular expression strings you can also
 use one of the following:

<ul>
 <li>'&lt;CondPattern' (lexicographically
 precedes) 
 Treats the CondPattern as a plain string and
 compares it lexicographically to TestString. True if
 TestString lexicographically precedes
 CondPattern.</li>

<li>'&gt;CondPattern' (lexicographically
 follows) 
 Treats the CondPattern as a plain string and
 compares it lexicographically to TestString. True if
 TestString lexicographically follows
 CondPattern.</li>

<li>'=CondPattern' (lexicographically
 equal) 
 Treats the CondPattern as a plain string and
 compares it lexicographically to TestString. True if
 TestString is lexicographically equal to
 CondPattern (the two strings are exactly
 equal, character for character). If CondPattern
 is <code>""</code> (two quotation marks) this
 compares TestString to the empty string.</li>

<li>'-d' (is
 directory) 
 Treats the TestString as a pathname and tests
 whether or not it exists, and is a directory.</li>

<li>'-f' (is regular
 file) 
 Treats the TestString as a pathname and tests
 whether or not it exists, and is a regular file.</li>

<li>'-s' (is regular file, with
 size) 
 Treats the TestString as a pathname and tests
 whether or not it exists, and is a regular file with size greater
 than zero.</li>

</ul>

Note:
 All of these tests can
 also be prefixed by an exclamation mark ('!') to
 negate their meaning.

</li>

<li>You can also set special flags for
 CondPattern by appending
 <code>[</code>flags<code>]</code>
 as the third argument to the <code>RewriteCond</code>
 directive, where flags is a comma-separated list of any of the
 following flags:

<ul>
 <li>'<code>nocase|NC</code>'
 (no case) 
 This makes the test case-insensitive - differences
 between 'A-Z' and 'a-z' are ignored, both in the
 expanded TestString and the CondPattern.
 This flag is effective only for comparisons between
 TestString and CondPattern. It has no
 effect on file system and subrequest checks.</li>

<li>
 '<code>ornext|OR</code>'
 (or next condition) 
 Use this to combine rule conditions with a local OR
 instead of the implicit AND. Typical example:

<div class="codeBox"><pre><code>RewriteCond %{REMOTE_HOST} ^host1.* [OR]
RewriteCond %{REMOTE_HOST} ^host2.* [OR]
RewriteCond %{REMOTE_HOST} ^host3.*
RewriteRule ...some special stuff for any of these hosts...</code></pre></div>

Without this flag you would have to write the condition/rule
 pair three times.
 </li>
 </ul>
 </li>
 </ol>

Example:

To rewrite the Homepage of a site according to the
 ``<code>User-Agent:</code>'' header of the request, you can
 use the following:

<div class="codeBox"><pre><code>RewriteCond %{HTTP_USER_AGENT} ^Mozilla.*
RewriteRule ^/$ /homepage.max.html [L]

RewriteCond  %{HTTP_USER_AGENT}  ^Lynx.*
RewriteRule  ^/$                 /homepage.min.html  [L]

RewriteRule ^/$ /homepage.std.html [L]</code></pre></div>

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.

</div></div>

<div class="subsection"><h4 id="RewriteMap">RewriteMap</h4><div class="text">

Syntax: <code>RewriteMap name rewriteMapClassName optionalParameters</code>

The <code>rewriteMapClassName</code> value also allows special values:
 <ul>
 <li><code>int:toupper</code>: Special map converting passed values to upper case</li>
 <li><code>int:tolower</code>: Special map converting passed values to lower case</li>
 <li><code>int:escape</code>: URL escape the passed value</li>
 <li><code>int:unescape</code>: URL unescape the passed value</li>
 </ul>

The maps are implemented using an interface that users must implement. Its class
 name is <code>org.apache.catalina.valves.rewrite.RewriteMap</code>, and its code is:

<div class="codeBox"><pre><code>package org.apache.catalina.valves.rewrite;

public interface RewriteMap {
 public String setParameters(String params);
 public String lookup(String key);
}</code></pre></div>

</div></div>

<div class="subsection"><h4 id="RewriteRule">RewriteRule</h4><div class="text">

Syntax: <code>RewriteRule Pattern Substitution</code>

The RewriteRule directive is the real
 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.

Pattern is a perl compatible regular
 expression, 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,
 which may already have matched a previous rule, and have been
 altered.

Security warning: Due to the way Java's
 regex matching is done, poorly formed regex patterns are vulnerable
 to "catastrophic backtracking", also known as "regular expression
 denial of service" or ReDoS. Therefore, extra caution should be used
 for RewriteRule patterns. In general it is difficult to automatically
 detect such vulnerable regex, and so a good defense is to read a bit
 on the subject of catastrophic backtracking. A good reference is the
 <a href="https://www.owasp.org/index.php/Regular_expression_Denial_of_Service_-_ReDoS">
 OWASP ReDoS guide</a>.

Some hints on the syntax of regular
 expressions:

<pre>
Text:
 <code>.</code> Any single character
 <code>[</code>chars<code>]</code> Character class: Any character of the class ``chars''
 <code>[^</code>chars<code>]</code> Character class: Not a character of the class ``chars''
 text1<code>|</code>text2 Alternative: text1 or text2

Quantifiers:
 <code>?</code> 0 or 1 occurrences of the preceding text
 <code>*</code> 0 or N occurrences of the preceding text (N &gt; 0)
 <code>+</code> 1 or N occurrences of the preceding text (N &gt; 1)

Grouping:
 <code>(</code>text<code>)</code> Grouping of text
 (used either to set the borders of an alternative as above, or
 to make backreferences, where the Nth group can
 be referred to on the RHS of a RewriteRule as <code>$</code>N)

Anchors:
 <code>^</code> Start-of-line anchor
 <code>$</code> End-of-line anchor

Escaping:
 <code>\</code>char escape the given char
 (for instance, to specify the chars "<code>.[]()</code>" etc.)
</pre>

For more information about regular expressions, have a look at the
 perl regular expression manpage ("<a href="https://perldoc.perl.org/perlre.html">perldoc
 perlre</a>"). If you are interested in more detailed
 information about regular expressions and their variants
 (POSIX regex etc.) the following book is dedicated to this topic:

Mastering Regular Expressions, 2nd Edition 
 Jeffrey E.F. Friedl 
 O'Reilly &amp; Associates, Inc. 2002 
 ISBN 978-0-596-00289-3

In the rules, the NOT character
 ('<code>!</code>') is also available as a possible pattern
 prefix. This enables you to negate a pattern; to say, for instance:
 ``if the current URL does NOT match this
 pattern''. This can be used for exceptional cases, where
 it is easier to match the negative pattern, or as a last
 default rule.

Note: 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 (i.e., 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!

The substitution of a
 rewrite rule is the string which is substituted for (or
 replaces) the original URL which Pattern
 matched. In addition to plain text, it can include

<ol>
 <li>back-references (<code>$N</code>) to the RewriteRule
 pattern</li>

<li>back-references (<code>%N</code>) to the last matched
 RewriteCond pattern</li>

<li>server-variables as in rule condition test-strings
 (<code>%{VARNAME}</code>)</li>

<li><a href="#mapfunc">mapping-function</a> calls
 (<code>${mapname:key|default}</code>)</li>
 </ol>
 Back-references are identifiers of the form
 <code>$</code>N
 (N=0..9), which will be replaced
 by the contents of the Nth group of the
 matched Pattern. The server-variables are the same
 as for the TestString 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 above.

As already mentioned, all rewrite rules are
 applied to the Substitution (in the order in which
 they are defined
 in the config file). The URL is completely
 replaced by the Substitution and the
 rewriting process continues until all rules have been applied,
 or it is explicitly terminated by a
 <code>L</code> flag.

The special characters <code>$</code> and <code>%</code> can
 be quoted by prepending them with a backslash character
 <code>\</code>.

There is a special substitution string named
 '<code>-</code>' which means: NO
 substitution! This is useful in providing
 rewriting rules which only match
 URLs but do not substitute anything for them. It is commonly used
 in conjunction with the C (chain) flag, in order
 to apply more than one pattern before substitution occurs.

Unlike newer mod_rewrite versions, the Tomcat rewrite valve does
 not automatically support absolute URLs (the specific redirect flag
 must be used to be able to specify an absolute URLs, see below)
 or direct file serving.

Additionally you can set special flags for Substitution by
 appending <code>[</code>flags<code>]</code>
 as the third argument to the <code>RewriteRule</code>
 directive. Flags is a comma-separated list of any of the
 following flags:

<ul>
 <li>'<code>chain|C</code>'
 (chained with next rule) 
 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
 matches, then processing continues as usual -
 the flag has no effect. If the rule does
 not match, then all following chained
 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>

<li>
 '<code>cookie|CO=</code>NAME:VAL:domain[:lifetime[:path]]'
 (set cookie) 
 This sets a cookie in the client's browser. The cookie's name
 is specified by NAME and the value is
 VAL. The domain field is the domain of the
 cookie, such as '.apache.org', the optional lifetime
 is the lifetime of the cookie in minutes, and the optional
 path is the path of the cookie</li>

<li>
 '<code>env|E=</code>VAR:VAL'
 (set environment variable) 
 This forces a request attribute named VAR to
 be set to the value VAL, where VAL 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.</li>

<li>'<code>forbidden|F</code>' (force URL
 to be forbidden) 
 This forces the current URL to be forbidden - it immediately
 sends back an HTTP response of 403 (FORBIDDEN).
 Use this flag in conjunction with
 appropriate RewriteConds to conditionally block some
 URLs.</li>

<li>'<code>gone|G</code>' (force URL to be
 gone) 
 This forces the current URL to be gone - it
 immediately sends back an HTTP response of 410 (GONE). Use
 this flag to mark pages which no longer exist as gone.</li>

<li>
 '<code>host|H</code>=Host'
 (apply rewriting to host) 
 Rather that rewrite the URL, the virtual host will be
 rewritten.</li>

<li>'<code>last|L</code>'
 (last rule) 
 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 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, e.g.,
 '<code>/e/www/</code>'.</li>

<li>'<code>next|N</code>'
 (next round) 
 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. 
 Be careful not to create an infinite
 loop!</li>

<li>'<code>nocase|NC</code>'
 (no case) 
 This makes the Pattern case-insensitive,
 ignoring difference between 'A-Z' and
 'a-z' when Pattern is matched against the current
 URL.</li>

<li>
 '<code>noescape|NE</code>'
 (no URI escaping of
 output) 
 This flag prevents the rewrite valve 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 happening. This allows percent symbols to appear in
 the output, as in
 <div class="codeBox"><pre><code>RewriteRule /foo/(.*) /bar?arg=P1\%3d$1 [R,NE]</code></pre></div>
 which would turn '<code>/foo/zed</code>' into a safe
 request for '<code>/bar?arg=P1=zed</code>'.
 </li>

<li>'<code>qsappend|QSA</code>'
 (query string
 append) 
 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>'<code>redirect|R</code>
 [=code]' (force 
 redirect) 
 Prefix Substitution with
 <code>http://thishost[:thisport]/</code> (which makes the
 new URL a URI) to force a external redirection. If no
 code is given, an HTTP response of 302 (FOUND, previously MOVED
 TEMPORARILY) will be returned. If you want to use other response
 codes in the range 300-399, 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>user, etc. 
 Note: 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>'<code>skip|S</code>=num'
 (skip next rule(s)) 
 This flag forces the rewriting engine to skip the next
 num 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 not the same as the
 'chain|C' flag!)</li>

<li>
 '<code>type|T</code>=MIME-type'
 (force MIME type) 
 Force the MIME-type of the target file to be
 MIME-type. 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 displayed by <code>mod_php</code> if they are called with
 the <code>.phps</code> extension:
 <div class="codeBox"><pre><code>RewriteRule ^(.+\.php)s$ $1 [T=application/x-httpd-php-source]</code></pre></div>
 </li>
 </ul>

</div></div>

${this.title}

Code Editor : rewrite.html