1 <?xml version="1.0" encoding="ISO-8859-1"?>
2 <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
3 <html xmlns="http://www.w3.org/1999/xhtml" lang="en" xml:lang="en"><head>
4 <meta content="text/html; charset=ISO-8859-1" http-equiv="Content-Type" />
6 XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
7 This file is generated from xml source: DO NOT EDIT
8 XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
10 <title>mod_rewrite - Apache HTTP Server Version 2.5</title>
11 <link href="../style/css/manual.css" rel="stylesheet" media="all" type="text/css" title="Main stylesheet" />
12 <link href="../style/css/manual-loose-100pc.css" rel="alternate stylesheet" media="all" type="text/css" title="No Sidebar - Default font size" />
13 <link href="../style/css/manual-print.css" rel="stylesheet" media="print" type="text/css" /><link rel="stylesheet" type="text/css" href="../style/css/prettify.css" />
14 <script src="../style/scripts/prettify.min.js" type="text/javascript">
17 <link href="../images/favicon.ico" rel="shortcut icon" /></head>
19 <div id="page-header">
20 <p class="menu"><a href="../mod/">Modules</a> | <a href="../mod/quickreference.html">Directives</a> | <a href="http://wiki.apache.org/httpd/FAQ">FAQ</a> | <a href="../glossary.html">Glossary</a> | <a href="../sitemap.html">Sitemap</a></p>
21 <p class="apache">Apache HTTP Server Version 2.5</p>
22 <img alt="" src="../images/feather.png" /></div>
23 <div class="up"><a href="./"><img title="<-" alt="<-" src="../images/left.gif" /></a></div>
25 <a href="http://www.apache.org/">Apache</a> > <a href="http://httpd.apache.org/">HTTP Server</a> > <a href="http://httpd.apache.org/docs/">Documentation</a> > <a href="../">Version 2.5</a> > <a href="./">Modules</a></div>
26 <div id="page-content">
27 <div id="preamble"><h1>Apache Module mod_rewrite</h1>
29 <p><span>Available Languages: </span><a href="../en/mod/mod_rewrite.html" title="English"> en </a> |
30 <a href="../fr/mod/mod_rewrite.html" hreflang="fr" rel="alternate" title="Français"> fr </a></p>
32 <table class="module"><tr><th><a href="module-dict.html#Description">Description:</a></th><td>Provides a rule-based rewriting engine to rewrite requested
33 URLs on the fly</td></tr>
34 <tr><th><a href="module-dict.html#Status">Status:</a></th><td>Extension</td></tr>
35 <tr><th><a href="module-dict.html#ModuleIdentifier">Module Identifier:</a></th><td>rewrite_module</td></tr>
36 <tr><th><a href="module-dict.html#SourceFile">Source File:</a></th><td>mod_rewrite.c</td></tr></table>
39 <p>The <code class="module"><a href="../mod/mod_rewrite.html">mod_rewrite</a></code> module uses a rule-based rewriting
40 engine, based on a PCRE regular-expression parser, to rewrite requested URLs on
41 the fly. By default, <code class="module"><a href="../mod/mod_rewrite.html">mod_rewrite</a></code> maps a URL to a filesystem
42 path. However, it can also be used to redirect one URL to another URL, or
43 to invoke an internal proxy fetch.</p>
44 <p><code class="module"><a href="../mod/mod_rewrite.html">mod_rewrite</a></code> provides a flexible and powerful way to
45 manipulate URLs using an unlimited number of rules. Each rule can have an
46 unlimited number of attached rule conditions, to allow you to rewrite URL
47 based on server variables, environment variables, HTTP headers, or time
49 <p><code class="module"><a href="../mod/mod_rewrite.html">mod_rewrite</a></code> operates on the full URL path, including the
50 path-info section. A rewrite rule can be invoked in
51 <code>httpd.conf</code> or in <code>.htaccess</code>. The path generated
52 by a rewrite rule can include a query string, or can lead to internal
53 sub-processing, external request redirection, or internal proxy
56 <p>Further details, discussion, and examples, are provided in the
57 <a href="../rewrite/">detailed mod_rewrite documentation</a>.</p>
59 <div id="quickview"><h3>Topics</h3>
61 <li><img alt="" src="../images/down.gif" /> <a href="#logging">Logging</a></li>
62 </ul><h3 class="directives">Directives</h3>
64 <li><img alt="" src="../images/down.gif" /> <a href="#rewritebase">RewriteBase</a></li>
65 <li><img alt="" src="../images/down.gif" /> <a href="#rewritecond">RewriteCond</a></li>
66 <li><img alt="" src="../images/down.gif" /> <a href="#rewriteengine">RewriteEngine</a></li>
67 <li><img alt="" src="../images/down.gif" /> <a href="#rewritemap">RewriteMap</a></li>
68 <li><img alt="" src="../images/down.gif" /> <a href="#rewriteoptions">RewriteOptions</a></li>
69 <li><img alt="" src="../images/down.gif" /> <a href="#rewriterule">RewriteRule</a></li>
71 <h3>Bugfix checklist</h3><ul class="seealso"><li><a href="https://www.apache.org/dist/httpd/CHANGES_2.4">httpd changelog</a></li><li><a href="https://bz.apache.org/bugzilla/buglist.cgi?bug_status=__open__&list_id=144532&product=Apache%20httpd-2&query_format=specific&order=changeddate%20DESC%2Cpriority%2Cbug_severity&component=mod_rewrite">Known issues</a></li><li><a href="https://bz.apache.org/bugzilla/enter_bug.cgi?product=Apache%20httpd-2&component=mod_rewrite">Report a bug</a></li></ul><h3>See also</h3>
73 <li><a href="#comments_section">Comments</a></li></ul></div>
74 <div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
76 <h2><a name="logging" id="logging">Logging</a></h2>
78 <p><code class="module"><a href="../mod/mod_rewrite.html">mod_rewrite</a></code> offers detailed logging of its actions
79 at the <code>trace1</code> to <code>trace8</code> log levels. The
80 log level can be set specifically for <code class="module"><a href="../mod/mod_rewrite.html">mod_rewrite</a></code>
81 using the <code class="directive"><a href="../mod/core.html#loglevel">LogLevel</a></code> directive: Up to
82 level <code>debug</code>, no actions are logged, while <code>trace8</code>
83 means that practically all actions are logged.</p>
86 Using a high trace log level for <code class="module"><a href="../mod/mod_rewrite.html">mod_rewrite</a></code>
87 will slow down your Apache HTTP Server dramatically! Use a log
88 level higher than <code>trace2</code> only for debugging!
91 <div class="example"><h3>Example</h3><pre class="prettyprint lang-config">LogLevel alert rewrite:trace3</pre>
94 <div class="note"><h3>RewriteLog</h3>
95 <p>Those familiar with earlier versions of
96 <code class="module"><a href="../mod/mod_rewrite.html">mod_rewrite</a></code> will no doubt be looking for the
97 <code>RewriteLog</code> and <code>RewriteLogLevel</code>
98 directives. This functionality has been completely replaced by the
99 new per-module logging configuration mentioned above.
102 <p>To get just the <code class="module"><a href="../mod/mod_rewrite.html">mod_rewrite</a></code>-specific log
103 messages, pipe the log file through grep:</p>
104 <div class="example"><p><code>
105 tail -f error_log|fgrep '[rewrite:'
110 <div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
111 <div class="directive-section"><h2><a name="RewriteBase" id="RewriteBase">RewriteBase</a> <a name="rewritebase" id="rewritebase">Directive</a></h2>
112 <table class="directive">
113 <tr><th><a href="directive-dict.html#Description">Description:</a></th><td>Sets the base URL for per-directory rewrites</td></tr>
114 <tr><th><a href="directive-dict.html#Syntax">Syntax:</a></th><td><code>RewriteBase <em>URL-path</em></code></td></tr>
115 <tr><th><a href="directive-dict.html#Default">Default:</a></th><td><code>None</code></td></tr>
116 <tr><th><a href="directive-dict.html#Context">Context:</a></th><td>directory, .htaccess</td></tr>
117 <tr><th><a href="directive-dict.html#Override">Override:</a></th><td>FileInfo</td></tr>
118 <tr><th><a href="directive-dict.html#Status">Status:</a></th><td>Extension</td></tr>
119 <tr><th><a href="directive-dict.html#Module">Module:</a></th><td>mod_rewrite</td></tr>
121 <p>The <code class="directive">RewriteBase</code> directive specifies the
122 URL prefix to be used for per-directory (htaccess)
123 <code class="directive"><a href="#rewriterule">RewriteRule</a></code> directives that
124 substitute a relative path.</p>
125 <p> This directive is <em>required</em> when you use a relative path
126 in a substitution in per-directory (htaccess) context unless either
127 of the following conditions are true:</p>
129 <li> The original request, and the substitution, are underneath the
130 <code class="directive"><a href="../mod/core.html#documentroot">DocumentRoot</a></code>
131 (as opposed to reachable by other means, such as
132 <code class="directive"><a href="../mod/mod_alias.html#alias">Alias</a></code>).</li>
133 <li> The <em>filesystem</em> path to the directory containing the
134 <code class="directive"><a href="#rewriterule">RewriteRule</a></code>,
135 suffixed by the relative
136 substitution is also valid as a URL path on the server
138 <li> In Apache HTTP Server 2.4.16 and later, this directive may be
139 omitted when the request is mapped via
140 <code class="directive"><a href="../mod/mod_alias.html#alias">Alias</a></code>
141 or <code class="module"><a href="../mod/mod_userdir.html">mod_userdir</a></code>.</li>
144 <p> In the example below, <code class="directive">RewriteBase</code> is necessary
145 to avoid rewriting to http://example.com/opt/myapp-1.2.3/welcome.html
146 since the resource was not relative to the document root. This
147 misconfiguration would normally cause the server to look for an "opt"
148 directory under the document root.</p>
149 <pre class="prettyprint lang-config">DocumentRoot "/var/www/example.com"
150 AliasMatch "^/myapp" "/opt/myapp-1.2.3"
151 <Directory "/opt/myapp-1.2.3">
153 RewriteBase "/myapp/"
154 RewriteRule "^index\.html$" "welcome.html"
155 </Directory></pre>
160 <div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
161 <div class="directive-section"><h2><a name="RewriteCond" id="RewriteCond">RewriteCond</a> <a name="rewritecond" id="rewritecond">Directive</a></h2>
162 <table class="directive">
163 <tr><th><a href="directive-dict.html#Description">Description:</a></th><td>Defines a condition under which rewriting will take place
165 <tr><th><a href="directive-dict.html#Syntax">Syntax:</a></th><td><code> RewriteCond
166 <em>TestString</em> <em>CondPattern</em></code></td></tr>
167 <tr><th><a href="directive-dict.html#Context">Context:</a></th><td>server config, virtual host, directory, .htaccess</td></tr>
168 <tr><th><a href="directive-dict.html#Override">Override:</a></th><td>FileInfo</td></tr>
169 <tr><th><a href="directive-dict.html#Status">Status:</a></th><td>Extension</td></tr>
170 <tr><th><a href="directive-dict.html#Module">Module:</a></th><td>mod_rewrite</td></tr>
172 <p>The <code class="directive">RewriteCond</code> directive defines a
173 rule condition. One or more <code class="directive">RewriteCond</code>
174 can precede a <code class="directive"><a href="#rewriterule">RewriteRule</a></code>
175 directive. The following rule is then only used if both
176 the current state of the URI matches its pattern, <strong>and</strong> if these conditions are met.</p>
178 <p><em>TestString</em> is a string which can contain the
179 following expanded constructs in addition to plain text:</p>
183 <strong>RewriteRule backreferences</strong>: These are
184 backreferences of the form <strong><code>$N</code></strong>
185 (0 <= N <= 9). $1 to $9 provide access to the grouped
186 parts (in parentheses) of the pattern, from the
187 <code>RewriteRule</code> which is subject to the current
188 set of <code>RewriteCond</code> conditions. $0 provides
189 access to the whole string matched by that pattern.
192 <strong>RewriteCond backreferences</strong>: These are
193 backreferences of the form <strong><code>%N</code></strong>
194 (0 <= N <= 9). %1 to %9 provide access to the grouped
195 parts (again, in parentheses) of the pattern, from the last matched
196 <code>RewriteCond</code> in the current set
197 of conditions. %0 provides access to the whole string matched by
201 <strong>RewriteMap expansions</strong>: These are
202 expansions of the form <strong><code>${mapname:key|default}</code></strong>.
203 See <a href="#mapfunc">the documentation for
204 RewriteMap</a> for more details.
207 <strong>Server-Variables</strong>: These are variables of
209 <strong><code>%{</code> <em>NAME_OF_VARIABLE</em>
210 <code>}</code></strong>
211 where <em>NAME_OF_VARIABLE</em> can be a string taken
212 from the following list:
217 <th>HTTP headers:</th> <th>connection & request:</th> <th />
226 HTTP_PROXY_CONNECTION<br />
228 HTTP_USER_AGENT<br />
233 CONN_REMOTE_ADDR<br />
235 CONTEXT_DOCUMENT_ROOT<br />
245 SCRIPT_FILENAME<br />
252 <th>server internals:</th> <th>date and time:</th> <th>specials:</th>
264 SERVER_PROTOCOL<br />
265 SERVER_SOFTWARE<br />
281 CONN_REMOTE_ADDR<br />
285 REQUEST_FILENAME<br />
293 <p>These variables all
294 correspond to the similarly named HTTP
295 MIME-headers, C variables of the Apache HTTP Server or
296 <code>struct tm</code> fields of the Unix system.
297 Most are documented <a href="../expr.html#vars">here</a>
298 or elsewhere in the Manual or in the CGI specification.</p>
300 <p>SERVER_NAME and SERVER_PORT depend on the values of
301 <code class="directive"><a href="../mod/core.html#usecanonicalname">UseCanonicalName</a></code> and
302 <code class="directive"><a href="../mod/core.html#usecanonicalphysicalport">UseCanonicalPhysicalPort</a></code>
305 <p>Those that are special to mod_rewrite include those below.</p>
307 <dt><code>API_VERSION</code></dt>
309 <dd>This is the version of the Apache httpd module API
310 (the internal interface between server and
311 module) in the current httpd build, as defined in
312 include/ap_mmn.h. The module API version
313 corresponds to the version of Apache httpd in use (in
314 the release version of Apache httpd 1.3.14, for
315 instance, it is 19990320:10), but is mainly of
316 interest to module authors.</dd>
318 <dt><code>CONN_REMOTE_ADDR</code></dt>
320 <dd>Since 2.4.8: The peer IP address of the connection (see the
321 <code class="module"><a href="../mod/mod_remoteip.html">mod_remoteip</a></code> module).</dd>
323 <dt><code>HTTPS</code></dt>
325 <dd>Will contain the text "on" if the connection is
326 using SSL/TLS, or "off" otherwise. (This variable
327 can be safely used regardless of whether or not
328 <code class="module"><a href="../mod/mod_ssl.html">mod_ssl</a></code> is loaded).</dd>
330 <dt><code>IS_SUBREQ</code></dt>
332 <dd>Will contain the text "true" if the request
333 currently being processed is a sub-request,
334 "false" otherwise. Sub-requests may be generated
335 by modules that need to resolve additional files
336 or URIs in order to complete their tasks.</dd>
338 <dt><code>REMOTE_ADDR</code></dt>
340 <dd>The IP address of the remote host (see the
341 <code class="module"><a href="../mod/mod_remoteip.html">mod_remoteip</a></code> module).</dd>
343 <dt><code>REQUEST_FILENAME</code></dt>
345 <dd>The full local filesystem path to the file or
346 script matching the request, if this has already
347 been determined by the server at the time
348 <code>REQUEST_FILENAME</code> is referenced. Otherwise,
349 such as when used in virtual host context, the same
350 value as <code>REQUEST_URI</code>. Depending on the value of
351 <code class="directive"><a href="../mod/core.html#acceptpathinfo">AcceptPathInfo</a></code>, the
352 server may have only used some leading components of the
353 <code>REQUEST_URI</code> to map the request to a file.
356 <dt><code>REQUEST_SCHEME</code></dt>
358 <dd>Will contain the scheme of the request (usually
359 "http" or "https"). This value can be influenced with
360 <code class="directive"><a href="../mod/core.html#servername">ServerName</a></code>.</dd>
362 <dt><code>REQUEST_URI</code></dt>
364 <dd>The path component of the requested URI,
365 such as "/index.html". This notably excludes the
366 query string which is available as its own variable
367 named <code>QUERY_STRING</code>.</dd>
369 <dt><code>THE_REQUEST</code></dt>
371 <dd>The full HTTP request line sent by the
372 browser to the server (e.g., "<code>GET
373 /index.html HTTP/1.1</code>"). This does not
374 include any additional headers sent by the
375 browser. This value has not been unescaped
376 (decoded), unlike most other variables below.</dd>
382 <p>If the <em>TestString</em> has the special value <code>expr</code>,
383 the <em>CondPattern</em> will be treated as an
384 <a href="../expr.html">ap_expr</a>. HTTP headers referenced in the
385 expression will be added to the Vary header if the <code>novary</code>
386 flag is not given.</p>
388 <p>Other things you should be aware of:</p>
392 <p>The variables SCRIPT_FILENAME and REQUEST_FILENAME
393 contain the same value - the value of the
394 <code>filename</code> field of the internal
395 <code>request_rec</code> structure of the Apache HTTP Server.
396 The first name is the commonly known CGI variable name
397 while the second is the appropriate counterpart of
398 REQUEST_URI (which contains the value of the
399 <code>uri</code> field of <code>request_rec</code>).</p>
400 <p>If a substitution occurred and the rewriting continues,
401 the value of both variables will be updated accordingly.</p>
402 <p>If used in per-server context (<em>i.e.</em>, before the
403 request is mapped to the filesystem) SCRIPT_FILENAME and
404 REQUEST_FILENAME cannot contain the full local filesystem
405 path since the path is unknown at this stage of processing.
406 Both variables will initially contain the value of REQUEST_URI
407 in that case. In order to obtain the full local filesystem
408 path of the request in per-server context, use an URL-based
409 look-ahead <code>%{LA-U:REQUEST_FILENAME}</code> to determine
410 the final value of REQUEST_FILENAME.</p></li>
413 <code>%{ENV:variable}</code>, where <em>variable</em> can be
414 any environment variable, is also available.
415 This is looked-up via internal
416 Apache httpd structures and (if not found there) via
417 <code>getenv()</code> from the Apache httpd server process.</li>
420 <code>%{SSL:variable}</code>, where <em>variable</em> is the
421 name of an <a href="mod_ssl.html#envvars">SSL environment
422 variable</a>, can be used whether or not
423 <code class="module"><a href="../mod/mod_ssl.html">mod_ssl</a></code> is loaded, but will always expand to
424 the empty string if it is not. Example:
425 <code>%{SSL:SSL_CIPHER_USEKEYSIZE}</code> may expand to
426 <code>128</code>. These variables are available even without
427 setting the <code>StdEnvVars</code> option of the
428 <code class="directive"><a href="../mod/mod_ssl.html#ssloptions">SSLOptions</a></code> directive.</li>
431 <code>%{HTTP:header}</code>, where <em>header</em> can be
432 any HTTP MIME-header name, can always be used to obtain the
433 value of a header sent in the HTTP request.
434 Example: <code>%{HTTP:Proxy-Connection}</code> is
435 the value of the HTTP header
436 ``<code>Proxy-Connection:</code>''.
437 <p>If a HTTP header is used in a condition this header is added to
438 the Vary header of the response in case the condition evaluates
439 to true for the request. It is <strong>not</strong> added if the
440 condition evaluates to false for the request. Adding the HTTP header
441 to the Vary header of the response is needed for proper caching.</p>
442 <p>It has to be kept in mind that conditions follow a short circuit
443 logic in the case of the '<strong><code>ornext|OR</code></strong>' flag
444 so that certain conditions might not be evaluated at all.</p></li>
447 <a id="LA-U" name="LA-U"><code>%{LA-U:variable}</code></a>
448 can be used for look-aheads which perform
449 an internal (URL-based) sub-request to determine the final
450 value of <em>variable</em>. This can be used to access
451 variable for rewriting which is not available at the current
452 stage, but will be set in a later phase.
453 <p>For instance, to rewrite according to the
454 <code>REMOTE_USER</code> variable from within the
455 per-server context (<code>httpd.conf</code> file) you must
456 use <code>%{LA-U:REMOTE_USER}</code> - this
457 variable is set by the authorization phases, which come
458 <em>after</em> the URL translation phase (during which mod_rewrite
460 <p>On the other hand, because mod_rewrite implements
461 its per-directory context (<code>.htaccess</code> file) via
462 the Fixup phase of the API and because the authorization
463 phases come <em>before</em> this phase, you just can use
464 <code>%{REMOTE_USER}</code> in that context.</p></li>
467 <code>%{LA-F:variable}</code> can be used to perform an internal
468 (filename-based) sub-request, to determine the final value
469 of <em>variable</em>. Most of the time, this is the same as
473 <p><em>CondPattern</em> is the condition pattern,
474 a regular expression which is applied to the
475 current instance of the <em>TestString</em>.
476 <em>TestString</em> is first evaluated, before being matched against
477 <em>CondPattern</em>.</p>
479 <p><em>CondPattern</em> is usually a
480 <em>perl compatible regular expression</em>, but there is
481 additional syntax available to perform other useful tests against
482 the <em>Teststring</em>:</p>
485 <li>You can prefix the pattern string with a
486 '<code>!</code>' character (exclamation mark) to negate the result
487 of the condition, no matter what kind of <em>CondPattern</em> is used.
491 You can perform lexicographical string comparisons:
494 <dt><strong><CondPattern</strong></dt>
495 <dd>Lexicographically precedes<br />
496 Treats the <em>CondPattern</em> as a plain string and
497 compares it lexicographically to <em>TestString</em>. True if
498 <em>TestString</em> lexicographically precedes
499 <em>CondPattern</em>.</dd>
501 <dt><strong>>CondPattern</strong></dt>
502 <dd>Lexicographically follows<br />
503 Treats the <em>CondPattern</em> as a plain string and
504 compares it lexicographically to <em>TestString</em>. True if
505 <em>TestString</em> lexicographically follows
506 <em>CondPattern</em>.</dd>
508 <dt><strong>=CondPattern</strong></dt>
509 <dd>Lexicographically equal<br />
510 Treats the <em>CondPattern</em> as a plain string and
511 compares it lexicographically to <em>TestString</em>. True if
512 <em>TestString</em> is lexicographically equal to
513 <em>CondPattern</em> (the two strings are exactly
514 equal, character for character). If <em>CondPattern</em>
515 is <code>""</code> (two quotation marks) this
516 compares <em>TestString</em> to the empty string.</dd>
518 <dt><strong><=CondPattern</strong></dt>
519 <dd>Lexicographically less than or equal to<br />
520 Treats the <em>CondPattern</em> as a plain string and
521 compares it lexicographically to <em>TestString</em>. True
522 if <em>TestString</em> lexicographically precedes
523 <em>CondPattern</em>, or is equal to <em>CondPattern</em>
524 (the two strings are equal, character for character).</dd>
526 <dt><strong>>=CondPattern</strong></dt>
527 <dd>Lexicographically greater than or equal to<br />
528 Treats the <em>CondPattern</em> as a plain string and
529 compares it lexicographically to <em>TestString</em>. True
530 if <em>TestString</em> lexicographically follows
531 <em>CondPattern</em>, or is equal to <em>CondPattern</em>
532 (the two strings are equal, character for character).</dd>
537 You can perform integer comparisons:
540 <dt><strong>-eq</strong></dt>
541 <dd>Is numerically <strong>eq</strong>ual to<br />
542 The <em>TestString</em> is treated as an integer, and is
543 numerically compared to the <em>CondPattern</em>. True if
544 the two are numerically equal.</dd>
546 <dt><strong>-ge</strong></dt>
547 <dd>Is numerically <strong>g</strong>reater than or <strong>e</strong>qual to<br />
548 The <em>TestString</em> is treated as an integer, and is
549 numerically compared to the <em>CondPattern</em>. True if
550 the <em>TestString</em> is numerically greater than or equal
551 to the <em>CondPattern</em>.</dd>
553 <dt><strong>-gt</strong></dt>
554 <dd>Is numerically <strong>g</strong>reater <strong>t</strong>han<br />
555 The <em>TestString</em> is treated as an integer, and is
556 numerically compared to the <em>CondPattern</em>. True if
557 the <em>TestString</em> is numerically greater than
558 the <em>CondPattern</em>.</dd>
560 <dt><strong>-le</strong></dt>
561 <dd>Is numerically <strong>l</strong>ess than or <strong>e</strong>qual to<br />
562 The <em>TestString</em> is treated as an integer, and is
563 numerically compared to the <em>CondPattern</em>. True if
564 the <em>TestString</em> is numerically less than or equal
565 to the <em>CondPattern</em>. Avoid confusion with the
566 <strong>-l</strong> by using the <strong>-L</strong> or
567 <strong>-h</strong> variant.</dd>
569 <dt><strong>-lt</strong></dt>
570 <dd>Is numerically <strong>l</strong>ess <strong>t</strong>han<br />
571 The <em>TestString</em> is treated as an integer, and is
572 numerically compared to the <em>CondPattern</em>. True if
573 the <em>TestString</em> is numerically less than
574 the <em>CondPattern</em>. Avoid confusion with the
575 <strong>-l</strong> by using the <strong>-L</strong> or
576 <strong>-h</strong> variant.</dd>
578 <dt><strong>-ne</strong></dt>
579 <dd>Is numerically <strong>n</strong>ot <strong>e</strong>qual to<br />
580 The <em>TestString</em> is treated as an integer, and is
581 numerically compared to the <em>CondPattern</em>. True if
582 the two are numerically different. This is equivalent to
583 <code>!-eq</code>.</dd>
588 <li>You can perform various file attribute tests:
593 <dt><strong>-d</strong></dt>
595 <dd>Is <strong>d</strong>irectory.<br />
596 Treats the <em>TestString</em> as a pathname and tests
597 whether or not it exists, and is a directory.
600 <dt><strong>-f</strong></dt>
602 <dd>Is regular <strong>f</strong>ile.<br />
604 Treats the <em>TestString</em> as a pathname and tests
605 whether or not it exists, and is a regular file.
608 <dt><strong>-F</strong></dt>
610 <dd>Is existing file, via subrequest.<br />
611 Checks whether or not <em>TestString</em> is a valid file,
612 accessible via all the server's currently-configured
613 access controls for that path. This uses an internal
614 subrequest to do the check, so use it with care -
615 it can impact your server's performance!
618 <dt><strong>-h</strong></dt>
619 <dd>Is symbolic link, bash convention.<br />
620 See <strong>-l</strong>.
623 <dt><strong>-l</strong></dt>
625 <dd>Is symbolic <strong>l</strong>ink.<br />
626 Treats the <em>TestString</em> as a pathname and tests
627 whether or not it exists, and is a symbolic link. May also
628 use the bash convention of <strong>-L</strong> or
629 <strong>-h</strong> if there's a possibility of confusion
630 such as when using the <strong>-lt</strong> or
631 <strong>-le</strong> tests.
634 <dt><strong>-L</strong></dt>
635 <dd>Is symbolic link, bash convention.<br />
636 See <strong>-l</strong>.</dd>
638 <dt><strong>-s</strong></dt>
639 <dd>Is regular file, with <strong>s</strong>ize.<br />
640 Treats the <em>TestString</em> as a pathname and tests
641 whether or not it exists, and is a regular file with size greater
644 <dt><strong>-U</strong></dt>
645 <dd><p>Is existing URL, via subrequest.<br />
646 Checks whether or not <em>TestString</em> is a valid URL,
647 accessible via all the server's currently-configured
648 access controls for that path. This uses an internal
649 subrequest to do the check, so use it with care -
650 it can impact your server's performance!</p>
651 <p> This flag <em>only</em> returns information about things
652 like access control, authentication, and authorization. This flag
653 <em>does not</em> return information about the status code the
654 configured handler (static file, CGI, proxy, etc.) would have
657 <dt><strong>-x</strong></dt>
658 <dd>Has e<strong>x</strong>ecutable permissions.<br />
659 Treats the <em>TestString</em> as a pathname and tests
660 whether or not it exists, and has executable permissions.
661 These permissions are determined according to
662 the underlying OS.</dd>
668 <pre class="prettyprint lang-config">RewriteCond /var/www/%{REQUEST_URI} !-f
669 RewriteRule ^(.+) /other/archive/$1 [R]</pre>
675 <p>If the <em>TestString</em> has the special value <code>expr</code>, the
676 <em>CondPattern</em> will be treated as an
677 <a href="../expr.html">ap_expr</a>.</p>
680 In the below example, <code>-strmatch</code> is used to
681 compare the <code>REFERER</code> against the site hostname,
682 to block unwanted hotlinking.
685 <pre class="prettyprint lang-config">RewriteCond expr "! %{HTTP_REFERER} -strmatch '*://%{HTTP_HOST}/*'"
686 RewriteRule "^/images" "-" [F]</pre>
690 <li>You can also set special flags for
691 <em>CondPattern</em> by appending
692 <strong><code>[</code><em>flags</em><code>]</code></strong>
693 as the third argument to the <code>RewriteCond</code>
694 directive, where <em>flags</em> is a comma-separated list of any of the
698 <li>'<strong><code>nocase|NC</code></strong>'
699 (<strong>n</strong>o <strong>c</strong>ase)<br />
700 This makes the test case-insensitive - differences
701 between 'A-Z' and 'a-z' are ignored, both in the
702 expanded <em>TestString</em> and the <em>CondPattern</em>.
703 This flag is effective only for comparisons between
704 <em>TestString</em> and <em>CondPattern</em>. It has no
705 effect on filesystem and subrequest checks.</li>
708 '<strong><code>ornext|OR</code></strong>'
709 (<strong>or</strong> next condition)<br />
710 Use this to combine rule conditions with a local OR
711 instead of the implicit AND. Typical example:
713 <pre class="prettyprint lang-config">RewriteCond "%{REMOTE_HOST}" "^host1" [OR]
714 RewriteCond "%{REMOTE_HOST}" "^host2" [OR]
715 RewriteCond "%{REMOTE_HOST}" "^host3"
716 RewriteRule ...some special stuff for any of these hosts...</pre>
719 Without this flag you would have to write the condition/rule
723 <li>'<strong><code>novary|NV</code></strong>'
724 (<strong>n</strong>o <strong>v</strong>ary)<br />
725 If a HTTP header is used in the condition, this flag prevents
726 this header from being added to the Vary header of the response. <br />
727 Using this flag might break proper caching of the response if
728 the representation of this response varies on the value of this header.
729 So this flag should be only used if the meaning of the Vary header
736 <p><strong>Example:</strong></p>
738 <p>To rewrite the Homepage of a site according to the
739 ``<code>User-Agent:</code>'' header of the request, you can
740 use the following: </p>
742 <pre class="prettyprint lang-config">RewriteCond "%{HTTP_USER_AGENT}" "(iPhone|Blackberry|Android)"
743 RewriteRule "^/$" "/homepage.mobile.html" [L]
745 RewriteRule "^/$" "/homepage.std.html" [L]</pre>
748 <p>Explanation: If you use a browser which identifies itself
749 as a mobile browser (note that the example is incomplete, as
750 there are many other mobile platforms), the mobile version of
751 the homepage is served. Otherwise, the standard page is served.
756 <div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
757 <div class="directive-section"><h2><a name="RewriteEngine" id="RewriteEngine">RewriteEngine</a> <a name="rewriteengine" id="rewriteengine">Directive</a></h2>
758 <table class="directive">
759 <tr><th><a href="directive-dict.html#Description">Description:</a></th><td>Enables or disables runtime rewriting engine</td></tr>
760 <tr><th><a href="directive-dict.html#Syntax">Syntax:</a></th><td><code>RewriteEngine on|off</code></td></tr>
761 <tr><th><a href="directive-dict.html#Default">Default:</a></th><td><code>RewriteEngine off</code></td></tr>
762 <tr><th><a href="directive-dict.html#Context">Context:</a></th><td>server config, virtual host, directory, .htaccess</td></tr>
763 <tr><th><a href="directive-dict.html#Override">Override:</a></th><td>FileInfo</td></tr>
764 <tr><th><a href="directive-dict.html#Status">Status:</a></th><td>Extension</td></tr>
765 <tr><th><a href="directive-dict.html#Module">Module:</a></th><td>mod_rewrite</td></tr>
768 <p>The <code class="directive">RewriteEngine</code> directive enables or
769 disables the runtime rewriting engine. If it is set to
770 <code>off</code> this module does no runtime processing at
771 all. It does not even update the <code>SCRIPT_URx</code>
772 environment variables.</p>
774 <p>Use this directive to disable rules in a particular context,
775 rather than commenting out all the <code class="directive"><a href="#rewriterule">RewriteRule</a></code> directives.</p>
777 <p>Note that rewrite configurations are not
778 inherited by virtual hosts. This means that you need to have a
779 <code>RewriteEngine on</code> directive for each virtual host
780 in which you wish to use rewrite rules.</p>
782 <p><code class="directive"><a href="#rewritemap">RewriteMap</a></code> directives
783 of the type <code>prg</code>
784 are not started during server initialization if they're defined in a
785 context that does not have <code class="directive">RewriteEngine</code> set to
789 <div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
790 <div class="directive-section"><h2><a name="RewriteMap" id="RewriteMap">RewriteMap</a> <a name="rewritemap" id="rewritemap">Directive</a></h2>
791 <table class="directive">
792 <tr><th><a href="directive-dict.html#Description">Description:</a></th><td>Defines a mapping function for key-lookup</td></tr>
793 <tr><th><a href="directive-dict.html#Syntax">Syntax:</a></th><td><code>RewriteMap <em>MapName</em> <em>MapType</em>:<em>MapSource</em>
794 <em>MapTypeOptions</em>
796 <tr><th><a href="directive-dict.html#Context">Context:</a></th><td>server config, virtual host</td></tr>
797 <tr><th><a href="directive-dict.html#Status">Status:</a></th><td>Extension</td></tr>
798 <tr><th><a href="directive-dict.html#Module">Module:</a></th><td>mod_rewrite</td></tr>
800 <p>The <code class="directive">RewriteMap</code> directive defines a
801 <em>Rewriting Map</em> which can be used inside rule
802 substitution strings by the mapping-functions to
803 insert/substitute fields through a key lookup. The source of
804 this lookup can be of various types.</p>
806 <p>The <a id="mapfunc" name="mapfunc"><em>MapName</em></a> is
807 the name of the map and will be used to specify a
808 mapping-function for the substitution strings of a rewriting
809 rule via one of the following constructs:</p>
812 <strong><code>${</code> <em>MapName</em> <code>:</code>
813 <em>LookupKey</em> <code>}</code><br />
814 <code>${</code> <em>MapName</em> <code>:</code>
815 <em>LookupKey</em> <code>|</code> <em>DefaultValue</em>
816 <code>}</code></strong>
819 <p>When such a construct occurs, the map <em>MapName</em> is
820 consulted and the key <em>LookupKey</em> is looked-up. If the
821 key is found, the map-function construct is substituted by
822 <em>SubstValue</em>. If the key is not found then it is
823 substituted by <em>DefaultValue</em> or by the empty string
824 if no <em>DefaultValue</em> was specified. Empty values
825 behave as if the key was absent, therefore it is not possible
826 to distinguish between empty-valued keys and absent keys.</p>
828 <p>For example, you might define a
829 <code class="directive">RewriteMap</code> as:</p>
831 <pre class="prettyprint lang-config">RewriteMap examplemap "txt:/path/to/file/map.txt"</pre>
834 <p>You would then be able to use this map in a
835 <code class="directive">RewriteRule</code> as follows:</p>
837 <pre class="prettyprint lang-config">RewriteRule "^/ex/(.*)" "${examplemap:$1}"</pre>
840 <p>The meaning of the <em>MapTypeOptions</em> argument depends on
841 particular <em>MapType</em>. See the
842 <a href="../rewrite/rewritemap.html">Using RewriteMap</a> for
843 more information.</p>
845 <p>The following combinations for <em>MapType</em> and
846 <em>MapSource</em> can be used:</p>
851 <dd>A plain text file containing space-separated key-value
852 pairs, one per line. (<a href="../rewrite/rewritemap.html#txt">Details ...</a>)</dd>
855 <dd>Randomly selects an entry from a plain text file (<a href="../rewrite/rewritemap.html#rnd">Details ...</a>)</dd>
858 <dd>Looks up an entry in a dbm file containing name, value
859 pairs. Hash is constructed from a plain text file format using
860 the <code><a href="../programs/httxt2dbm.html">httxt2dbm</a></code>
861 utility. (<a href="../rewrite/rewritemap.html#dbm">Details ...</a>)</dd>
864 <dd>One of the four available internal functions provided by
865 <code>RewriteMap</code>: toupper, tolower, escape or
866 unescape. (<a href="../rewrite/rewritemap.html#int">Details ...</a>)</dd>
869 <dd>Calls an external program or script to process the
870 rewriting. (<a href="../rewrite/rewritemap.html#prg">Details ...</a>)</dd>
872 <dt>dbd or fastdbd</dt>
873 <dd>A SQL SELECT statement to be performed to look up the
874 rewrite target. (<a href="../rewrite/rewritemap.html#dbd">Details ...</a>)</dd>
877 <p>Further details, and numerous examples, may be found in the <a href="../rewrite/rewritemap.html">RewriteMap HowTo</a></p>
881 <div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
882 <div class="directive-section"><h2><a name="RewriteOptions" id="RewriteOptions">RewriteOptions</a> <a name="rewriteoptions" id="rewriteoptions">Directive</a></h2>
883 <table class="directive">
884 <tr><th><a href="directive-dict.html#Description">Description:</a></th><td>Sets some special options for the rewrite engine</td></tr>
885 <tr><th><a href="directive-dict.html#Syntax">Syntax:</a></th><td><code>RewriteOptions <var>Options</var></code></td></tr>
886 <tr><th><a href="directive-dict.html#Context">Context:</a></th><td>server config, virtual host, directory, .htaccess</td></tr>
887 <tr><th><a href="directive-dict.html#Override">Override:</a></th><td>FileInfo</td></tr>
888 <tr><th><a href="directive-dict.html#Status">Status:</a></th><td>Extension</td></tr>
889 <tr><th><a href="directive-dict.html#Module">Module:</a></th><td>mod_rewrite</td></tr>
892 <p>The <code class="directive">RewriteOptions</code> directive sets some
893 special options for the current per-server or per-directory
894 configuration. The <em>Option</em> string can currently
895 only be one of the following:</p>
898 <dt><code>Inherit</code></dt>
901 <p>This forces the current configuration to inherit the
902 configuration of the parent. In per-virtual-server context,
903 this means that the maps, conditions and rules of the main
904 server are inherited. In per-directory context this means
905 that conditions and rules of the parent directory's
906 <code>.htaccess</code> configuration or
907 <code class="directive"><a href="../mod/core.html#directory"><Directory></a></code>
908 sections are inherited. The inherited rules are virtually copied
909 to the section where this directive is being used. If used in
910 combination with local rules, the inherited rules are copied behind
911 the local rules. The position of this directive - below or above
912 of local rules - has no influence on this behavior. If local
913 rules forced the rewriting to stop, the inherited rules won't
916 <div class="warning">
917 Rules inherited from the parent scope are applied
918 <strong>after</strong> rules specified in the child scope.
922 <dt><code>InheritBefore</code></dt>
924 <p> Like <code>Inherit</code> above, but the rules from the parent scope
925 are applied <strong>before</strong> rules specified in the child scope.<br />
926 Available in Apache HTTP Server 2.3.10 and later.</p>
929 <dt><code>InheritDown</code></dt>
932 <p>If this option is enabled, all child configurations will inherit
933 the configuration of the current configuration. It is equivalent to
934 specifying <code>RewriteOptions Inherit</code> in all child
935 configurations. See the <code>Inherit</code> option for more details
936 on how the parent-child relationships are handled.<br />
937 Available in Apache HTTP Server 2.4.8 and later.</p>
940 <dt><code>InheritDownBefore</code></dt>
943 <p>Like <code>InheritDown</code> above, but the rules from the current
944 scope are applied <strong>before</strong> rules specified in any child's
946 Available in Apache HTTP Server 2.4.8 and later.</p>
949 <dt><code>IgnoreInherit</code></dt>
952 <p>This option forces the current and child configurations to ignore
953 all rules that would be inherited from a parent specifying
954 <code>InheritDown</code> or <code>InheritDownBefore</code>.<br />
955 Available in Apache HTTP Server 2.4.8 and later.</p>
958 <dt><code>AllowNoSlash</code></dt>
960 <p>By default, <code class="module"><a href="../mod/mod_rewrite.html">mod_rewrite</a></code> will ignore URLs that map to a
961 directory on disk but lack a trailing slash, in the expectation that
962 the <code class="module"><a href="../mod/mod_dir.html">mod_dir</a></code> module will issue the client with a redirect to
963 the canonical URL with a trailing slash.</p>
965 <p>When the <code class="directive"><a href="../mod/mod_dir.html#directoryslash">DirectorySlash</a></code> directive
966 is set to off, the <code>AllowNoSlash</code> option can be enabled to ensure
967 that rewrite rules are no longer ignored. This option makes it possible to
968 apply rewrite rules within .htaccess files that match the directory without
969 a trailing slash, if so desired.<br />
970 Available in Apache HTTP Server 2.4.0 and later.</p>
973 <dt><code>AllowAnyURI</code></dt>
976 <p>When <code class="directive"><a href="#rewriterule">RewriteRule</a></code>
977 is used in <code>VirtualHost</code> or server context with
978 version 2.2.22 or later of httpd, <code class="module"><a href="../mod/mod_rewrite.html">mod_rewrite</a></code>
979 will only process the rewrite rules if the request URI is a <a href="directive-dict.html#Syntax">URL-path</a>. This avoids
980 some security issues where particular rules could allow
981 "surprising" pattern expansions (see <a href="http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2011-3368">CVE-2011-3368</a>
982 and <a href="http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2011-4317">CVE-2011-4317</a>).
983 To lift the restriction on matching a URL-path, the
984 <code>AllowAnyURI</code> option can be enabled, and
985 <code class="module"><a href="../mod/mod_rewrite.html">mod_rewrite</a></code> will apply the rule set to any
986 request URI string, regardless of whether that string matches
987 the URL-path grammar required by the HTTP specification.<br />
988 Available in Apache HTTP Server 2.4.3 and later.</p>
990 <div class="warning">
991 <h3>Security Warning</h3>
993 <p>Enabling this option will make the server vulnerable to
994 security issues if used with rewrite rules which are not
995 carefully authored. It is <strong>strongly recommended</strong>
996 that this option is not used. In particular, beware of input
997 strings containing the '<code>@</code>' character which could
998 change the interpretation of the transformed URI, as per the
1003 <dt><code>MergeBase</code></dt>
1006 <p>With this option, the value of <code class="directive"><a href="#rewritebase">RewriteBase</a></code> is copied from where it's explicitly defined
1007 into any sub-directory or sub-location that doesn't define its own
1008 <code class="directive"><a href="#rewritebase">RewriteBase</a></code>. This was the
1009 default behavior in 2.4.0 through 2.4.3, and the flag to restore it is
1010 available Apache HTTP Server 2.4.4 and later.</p>
1013 <dt><code>IgnoreContextInfo</code></dt>
1016 <p>When a relative substitution is made
1017 in directory (htaccess) context and <code class="directive"><a href="#rewritebase">RewriteBase</a></code> has not been set, this module uses some
1018 extended URL and filesystem context information to change the
1019 relative substitution back into a URL. Modules such as
1020 <code class="module"><a href="../mod/mod_userdir.html">mod_userdir</a></code> and <code class="module"><a href="../mod/mod_alias.html">mod_alias</a></code>
1021 supply this extended context info. Available in 2.4.16 and later.</p>
1027 <div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
1028 <div class="directive-section"><h2><a name="RewriteRule" id="RewriteRule">RewriteRule</a> <a name="rewriterule" id="rewriterule">Directive</a></h2>
1029 <table class="directive">
1030 <tr><th><a href="directive-dict.html#Description">Description:</a></th><td>Defines rules for the rewriting engine</td></tr>
1031 <tr><th><a href="directive-dict.html#Syntax">Syntax:</a></th><td><code>RewriteRule
1032 <em>Pattern</em> <em>Substitution</em> [<em>flags</em>]</code></td></tr>
1033 <tr><th><a href="directive-dict.html#Context">Context:</a></th><td>server config, virtual host, directory, .htaccess</td></tr>
1034 <tr><th><a href="directive-dict.html#Override">Override:</a></th><td>FileInfo</td></tr>
1035 <tr><th><a href="directive-dict.html#Status">Status:</a></th><td>Extension</td></tr>
1036 <tr><th><a href="directive-dict.html#Module">Module:</a></th><td>mod_rewrite</td></tr>
1038 <p>The <code class="directive">RewriteRule</code> directive is the real
1039 rewriting workhorse. The directive can occur more than once,
1040 with each instance defining a single rewrite rule. The
1041 order in which these rules are defined is important - this is the order
1042 in which they will be applied at run-time.</p>
1044 <p><a id="patterns" name="patterns"><em>Pattern</em></a> is
1045 a perl compatible <a id="regexp" name="regexp">regular
1046 expression</a>. On the first RewriteRule, it is matched against
1047 the (%-decoded) <a href="directive-dict.html#Syntax">URL-path</a>
1048 of the request, or, in per-directory context (see below), the URL
1049 path relative to that per-directory context. Subsequent patterns
1050 are matched against the output of the last matching RewriteRule.</p>
1052 <div class="note"><h3><a id="what_is_matched" name="what_is_matched">What is matched?</a></h3>
1053 <p>In <code class="directive"><a href="../mod/core.html#virtualhost">VirtualHost</a></code> context,
1054 The <em>Pattern</em> will initially be matched against the part of the
1055 URL after the hostname and port, and before the query string (e.g. "/app1/index.html").</p>
1057 <p>In <code class="directive"><a href="../mod/core.html#directory">Directory</a></code> and htaccess context,
1058 the <em>Pattern</em> will initially be matched against the
1059 <em>filesystem</em> path, after removing the prefix that led the server
1060 to the current <code class="directive">RewriteRule</code> (e.g. "app1/index.html"
1061 or "index.html" depending on where the directives are defined).</p>
1063 <p>If you wish to match against the hostname, port, or query string, use a
1064 <code class="directive"><a href="#rewritecond">RewriteCond</a></code> with the
1065 <code>%{HTTP_HOST}</code>, <code>%{SERVER_PORT}</code>, or
1066 <code>%{QUERY_STRING}</code> variables respectively.</p>
1068 <p>In any case, remember that regular expressions are substring
1069 matches. That is, you don't need the regex to describe the entire
1070 string, just the part that you wish to match. Thus, using a regex
1071 of <code>.</code> is often sufficient rather than <code>.*</code>,
1072 and the regex <code>abc</code> is <strong>not</strong> the same as
1073 <code>^abc$</code>.</p>
1077 <div class="note"><h3>Per-directory Rewrites</h3>
1079 <li>The rewrite engine may be used in <a href="../howto/htaccess.html">.htaccess</a> files and in <code class="directive"><a href="../mod/core.html#directory"><Directory></a></code> sections, with some additional
1082 <li>To enable the rewrite engine in this context, you need to set
1083 "<code>RewriteEngine On</code>" <strong>and</strong>
1084 "<code>Options FollowSymLinks</code>" must be enabled. If your
1085 administrator has disabled override of <code>FollowSymLinks</code> for
1086 a user's directory, then you cannot use the rewrite engine. This
1087 restriction is required for security reasons.</li>
1089 <li>When using the rewrite engine in <code>.htaccess</code> files the
1090 per-directory prefix (that is, the URI path that leads to the directory
1091 containing this <code>.htaccess</code> file)
1092 is <em>removed</em> for the RewriteRule pattern matching
1093 and <em>added</em> after any relative (not starting with a
1094 slash or protocol name) substitution encounters the end of a rule set.
1095 See the <code class="directive"><a href="#rewritebase">RewriteBase</a></code>
1096 directive for more information regarding what prefix will be added back to
1097 relative substitutions.</li>
1099 <li> If you wish to match against the full URL-path in a per-directory
1100 (htaccess) RewriteRule, use the <code>%{REQUEST_URI}</code> variable in
1101 a <code class="directive"><a href="#rewritecond">RewriteCond</a></code>.</li>
1103 <li>The removed prefix always ends with a slash, meaning the matching occurs against a string which
1104 <em>never</em> has a leading slash. Therefore, a <em>Pattern</em> with <code>^/</code> never
1105 matches in per-directory context.</li>
1107 <li>Although rewrite rules are syntactically permitted in <code class="directive"><a href="../mod/core.html#location"><Location></a></code> and <code class="directive"><a href="../mod/core.html#files"><Files></a></code> sections
1108 (including their regular expression counterparts), this
1109 should never be necessary and is unsupported. A likely feature
1110 to break in these contexts is relative substitutions.</li>
1114 <p>For some hints on <a class="glossarylink" href="../glossary.html#regex" title="see glossary">regular
1115 expressions</a>, see
1116 the <a href="../rewrite/intro.html#regex">mod_rewrite
1117 Introduction</a>.</p>
1119 <p>In mod_rewrite, the NOT character
1120 ('<code>!</code>') is also available as a possible pattern
1121 prefix. This enables you to negate a pattern; to say, for instance:
1122 ``<em>if the current URL does <strong>NOT</strong> match this
1123 pattern</em>''. This can be used for exceptional cases, where
1124 it is easier to match the negative pattern, or as a last
1127 <div class="note"><h3>Note</h3>
1128 When using the NOT character to negate a pattern, you cannot include
1129 grouped wildcard parts in that pattern. This is because, when the
1130 pattern does NOT match (ie, the negation matches), there are no
1131 contents for the groups. Thus, if negated patterns are used, you
1132 cannot use <code>$N</code> in the substitution string!
1135 <p>The <a id="rhs" name="rhs"><em>Substitution</em></a> of a
1136 rewrite rule is the string that replaces the original URL-path that
1137 was matched by <em>Pattern</em>. The <em>Substitution</em> may
1142 <dt>file-system path</dt>
1144 <dd>Designates the location on the file-system of the resource
1145 to be delivered to the client. Substitutions are only
1146 treated as a file-system path when the rule is configured in
1147 server (virtualhost) context and the first component of the
1148 path in the substitution exists in the file-system</dd>
1152 <dd>A <code class="directive"><a href="../mod/core.html#documentroot">DocumentRoot</a></code>-relative path to the
1153 resource to be served. Note that <code class="module"><a href="../mod/mod_rewrite.html">mod_rewrite</a></code>
1154 tries to guess whether you have specified a file-system path
1155 or a URL-path by checking to see if the first segment of the
1156 path exists at the root of the file-system. For example, if
1157 you specify a <em>Substitution</em> string of
1158 <code>/www/file.html</code>, then this will be treated as a
1159 URL-path <em>unless</em> a directory named <code>www</code>
1160 exists at the root or your file-system (or, in the case of
1161 using rewrites in a <code>.htaccess</code> file, relative to
1162 your document root), in which case it will
1163 be treated as a file-system path. If you wish other
1164 URL-mapping directives (such as <code class="directive"><a href="../mod/mod_alias.html#alias">Alias</a></code>) to be applied to the
1165 resulting URL-path, use the <code>[PT]</code> flag as
1166 described below.</dd>
1168 <dt>Absolute URL</dt>
1170 <dd>If an absolute URL is specified,
1171 <code class="module"><a href="../mod/mod_rewrite.html">mod_rewrite</a></code> checks to see whether the
1172 hostname matches the current host. If it does, the scheme and
1173 hostname are stripped out and the resulting path is treated as
1174 a URL-path. Otherwise, an external redirect is performed for
1175 the given URL. To force an external redirect back to the
1176 current host, see the <code>[R]</code> flag below.</dd>
1178 <dt><code>-</code> (dash)</dt>
1180 <dd>A dash indicates that no substitution should be performed
1181 (the existing path is passed through untouched). This is used
1182 when a flag (see below) needs to be applied without changing
1187 <p>In addition to plain text, the <em>Substitution</em> string can include</p>
1190 <li>back-references (<code>$N</code>) to the RewriteRule
1193 <li>back-references (<code>%N</code>) to the last matched
1194 RewriteCond pattern</li>
1196 <li>server-variables as in rule condition test-strings
1197 (<code>%{VARNAME}</code>)</li>
1199 <li><a href="#mapfunc">mapping-function</a> calls
1200 (<code>${mapname:key|default}</code>)</li>
1203 <p>Back-references are identifiers of the form
1204 <code>$</code><strong>N</strong>
1205 (<strong>N</strong>=0..9), which will be replaced
1206 by the contents of the <strong>N</strong>th group of the
1207 matched <em>Pattern</em>. The server-variables are the same
1208 as for the <em>TestString</em> of a
1209 <code class="directive"><a href="#rewritecond">RewriteCond</a></code>
1210 directive. The mapping-functions come from the
1211 <code class="directive"><a href="#rewritemap">RewriteMap</a></code>
1212 directive and are explained there.
1213 These three types of variables are expanded in the order above.</p>
1215 <p>Rewrite rules are applied to the results of previous rewrite
1216 rules, in the order in which they are defined
1217 in the config file. The URL-path or file-system path (see <a href="#what_is_matched">"What is matched?"</a>, above) is <strong>completely
1218 replaced</strong> by the <em>Substitution</em> and the
1219 rewriting process continues until all rules have been applied,
1220 or it is explicitly terminated by an
1221 <a href="../rewrite/flags.html#flag_l"><code><strong>L</strong></code> flag</a>,
1222 or other flag which implies immediate termination, such as
1223 <code><strong>END</strong></code> or
1224 <code><strong>F</strong></code>.</p>
1226 <div class="note"><h3>Modifying the Query String</h3>
1227 <p>By default, the query string is passed through unchanged. You
1228 can, however, create URLs in the substitution string containing
1229 a query string part. Simply use a question mark inside the
1230 substitution string to indicate that the following text should
1231 be re-injected into the query string. When you want to erase an
1232 existing query string, end the substitution string with just a
1233 question mark. To combine new and old query strings, use the
1234 <code>[QSA]</code> flag.</p>
1237 <p>Additionally you can set special <a name="rewriteflags" id="rewriteflags">actions</a> to be performed by
1238 appending <strong><code>[</code><em>flags</em><code>]</code></strong>
1239 as the third argument to the <code class="directive">RewriteRule</code>
1240 directive. <em>Flags</em> is a comma-separated list, surround by square
1241 brackets, of any of the flags in the following table. More
1242 details, and examples, for each flag, are available in the <a href="../rewrite/flags.html">Rewrite Flags document</a>.</p>
1244 <table class="bordered"><tr class="header"><th>Flag and syntax</th>
1249 <td>Escape non-alphanumeric characters in backreferences <em>before</em>
1250 applying the transformation. <em><a href="../rewrite/flags.html#flag_b">details ...</a></em></td>
1253 <td>backrefnoplus|BNP</td>
1254 <td>If backreferences are being escaped, spaces should be escaped to
1255 %20 instead of +. Useful when the backreference will be used in the
1256 path component rather than the query string.<em><a href="../rewrite/flags.html#flag_bnp">details ...</a></em></td>
1260 <td>Rule is chained to the following rule. If the rule fails,
1261 the rule(s) chained to it will be skipped. <em><a href="../rewrite/flags.html#flag_c">details ...</a></em></td>
1264 <td>cookie|CO=<em>NAME</em>:<em>VAL</em></td>
1265 <td>Sets a cookie in the client browser. Full syntax is:
1266 CO=<em>NAME</em>:<em>VAL</em>:<em>domain</em>[:<em>lifetime</em>[:<em>path</em>[:<em>secure</em>[:<em>httponly</em>]]]] <em><a href="../rewrite/flags.html#flag_co">details ...</a></em>
1270 <td>discardpath|DPI</td>
1271 <td>Causes the PATH_INFO portion of the rewritten URI to be
1272 discarded. <em><a href="../rewrite/flags.html#flag_dpi">details
1277 <td>Stop the rewriting process immediately and don't apply any
1278 more rules. Also prevents further execution of rewrite rules
1279 in per-directory and .htaccess context. (Available in 2.3.9 and later)
1280 <em><a href="../rewrite/flags.html#flag_end">details ...</a></em></td>
1283 <td>env|E=[!]<em>VAR</em>[:<em>VAL</em>]</td>
1284 <td>Causes an environment variable <em>VAR</em> to be set (to the
1285 value <em>VAL</em> if provided). The form !<em>VAR</em> causes
1286 the environment variable <em>VAR</em> to be unset.
1287 <em><a href="../rewrite/flags.html#flag_e">details ...</a></em></td>
1290 <td>forbidden|F</td>
1291 <td>Returns a 403 FORBIDDEN response to the client browser.
1292 <em><a href="../rewrite/flags.html#flag_f">details ...</a></em></td>
1296 <td>Returns a 410 GONE response to the client browser. <em><a href="../rewrite/flags.html#flag_g">details ...</a></em></td>
1299 <td>Handler|H=<em>Content-handler</em></td>
1300 <td>Causes the resulting URI to be sent to the specified
1301 <em>Content-handler</em> for processing. <em><a href="../rewrite/flags.html#flag_h">details ...</a></em></td>
1305 <td>Stop the rewriting process immediately and don't apply any
1306 more rules. Especially note caveats for per-directory and
1307 .htaccess context (see also the END flag). <em><a href="../rewrite/flags.html#flag_l">details ...</a></em></td>
1311 <td>Re-run the rewriting process, starting again with the first
1312 rule, using the result of the ruleset so far as a starting
1313 point. <em><a href="../rewrite/flags.html#flag_n">details
1318 <td>Makes the pattern comparison case-insensitive.
1319 <em><a href="../rewrite/flags.html#flag_nc">details ...</a></em></td>
1322 <td>noescape|NE</td>
1323 <td>Prevent mod_rewrite from applying hexcode escaping of
1324 special characters in the result of the rewrite. <em><a href="../rewrite/flags.html#flag_ne">details ...</a></em></td>
1327 <td>nosubreq|NS</td>
1328 <td>Causes a rule to be skipped if the current request is an
1329 internal sub-request. <em><a href="../rewrite/flags.html#flag_ns">details ...</a></em></td>
1333 <td>Force the substitution URL to be internally sent as a proxy
1334 request. <em><a href="../rewrite/flags.html#flag_p">details
1338 <td>passthrough|PT</td>
1339 <td>Forces the resulting URI to be passed back to the URL
1340 mapping engine for processing of other URI-to-filename
1341 translators, such as <code>Alias</code> or
1342 <code>Redirect</code>. <em><a href="../rewrite/flags.html#flag_pt">details ...</a></em></td>
1345 <td>qsappend|QSA</td>
1346 <td>Appends any query string from the original request URL to
1347 any query string created in the rewrite target.<em><a href="../rewrite/flags.html#flag_qsa">details ...</a></em></td>
1350 <td>qsdiscard|QSD</td>
1351 <td>Discard any query string attached to the incoming URI.
1352 <em><a href="../rewrite/flags.html#flag_qsd">details
1357 <td>Interpret the last (right-most) question mark as the query string
1358 delimeter, instead of the first (left-most) as normally used.
1359 Available in 2.4.19 and later.
1360 <em><a href="../rewrite/flags.html#flag_qsl">details
1364 <td>redirect|R[=<em>code</em>]</td>
1365 <td>Forces an external redirect, optionally with the specified
1366 HTTP status code. <em><a href="../rewrite/flags.html#flag_r">details ...</a></em>
1370 <td>skip|S=<em>num</em></td>
1371 <td>Tells the rewriting engine to skip the next <em>num</em>
1372 rules if the current rule matches. <em><a href="../rewrite/flags.html#flag_s">details ...</a></em></td>
1375 <td>type|T=<em>MIME-type</em></td>
1376 <td>Force the <a class="glossarylink" href="../glossary.html#mime-type" title="see glossary">MIME-type</a> of the target file
1377 to be the specified type. <em><a href="../rewrite/flags.html#flag_t">details ...</a></em></td>
1381 <div class="note"><h3>Home directory expansion</h3>
1382 <p> When the substitution string begins with a string
1383 resembling "/~user" (via explicit text or backreferences), mod_rewrite performs
1384 home directory expansion independent of the presence or configuration
1385 of <code class="module"><a href="../mod/mod_userdir.html">mod_userdir</a></code>.</p>
1387 <p> This expansion does not occur when the <em>PT</em>
1388 flag is used on the <code class="directive"><a href="#rewriterule">RewriteRule</a></code>
1393 <p>Here are all possible substitution combinations and their
1396 <p><strong>Inside per-server configuration
1397 (<code>httpd.conf</code>)<br />
1398 for request ``<code>GET
1399 /somepath/pathinfo</code>'':</strong><br />
1402 <table class="bordered"><tr class="header">
1404 <th>Resulting Substitution</th>
1407 <td>^/somepath(.*) otherpath$1</td>
1408 <td>invalid, not supported</td>
1411 <td>^/somepath(.*) otherpath$1 [R]</td>
1412 <td>invalid, not supported</td>
1415 <td>^/somepath(.*) otherpath$1 [P]</td>
1416 <td>invalid, not supported</td>
1419 <td>^/somepath(.*) /otherpath$1</td>
1420 <td>/otherpath/pathinfo</td>
1423 <td>^/somepath(.*) /otherpath$1 [R]</td>
1424 <td>http://thishost/otherpath/pathinfo via external redirection</td>
1427 <td>^/somepath(.*) /otherpath$1 [P]</td>
1428 <td>doesn't make sense, not supported</td>
1431 <td>^/somepath(.*) http://thishost/otherpath$1</td>
1432 <td>/otherpath/pathinfo</td>
1435 <td>^/somepath(.*) http://thishost/otherpath$1 [R]</td>
1436 <td>http://thishost/otherpath/pathinfo via external redirection</td>
1439 <td>^/somepath(.*) http://thishost/otherpath$1 [P]</td>
1440 <td>doesn't make sense, not supported</td>
1443 <td>^/somepath(.*) http://otherhost/otherpath$1</td>
1444 <td>http://otherhost/otherpath/pathinfo via external redirection</td>
1447 <td>^/somepath(.*) http://otherhost/otherpath$1 [R]</td>
1448 <td>http://otherhost/otherpath/pathinfo via external redirection (the [R] flag is redundant)</td>
1451 <td>^/somepath(.*) http://otherhost/otherpath$1 [P]</td>
1452 <td>http://otherhost/otherpath/pathinfo via internal proxy</td>
1456 <p><strong>Inside per-directory configuration for
1457 <code>/somepath</code><br />
1458 (<code>/physical/path/to/somepath/.htaccess</code>, with
1459 <code>RewriteBase "/somepath"</code>)<br />
1460 for request ``<code>GET
1461 /somepath/localpath/pathinfo</code>'':</strong><br />
1464 <table class="bordered"><tr class="header">
1466 <th>Resulting Substitution</th>
1469 <td>^localpath(.*) otherpath$1</td>
1470 <td>/somepath/otherpath/pathinfo</td>
1473 <td>^localpath(.*) otherpath$1 [R]</td>
1474 <td>http://thishost/somepath/otherpath/pathinfo via external
1478 <td>^localpath(.*) otherpath$1 [P]</td>
1479 <td>doesn't make sense, not supported</td>
1482 <td>^localpath(.*) /otherpath$1</td>
1483 <td>/otherpath/pathinfo</td>
1486 <td>^localpath(.*) /otherpath$1 [R]</td>
1487 <td>http://thishost/otherpath/pathinfo via external redirection</td>
1490 <td>^localpath(.*) /otherpath$1 [P]</td>
1491 <td>doesn't make sense, not supported</td>
1494 <td>^localpath(.*) http://thishost/otherpath$1</td>
1495 <td>/otherpath/pathinfo</td>
1498 <td>^localpath(.*) http://thishost/otherpath$1 [R]</td>
1499 <td>http://thishost/otherpath/pathinfo via external redirection</td>
1502 <td>^localpath(.*) http://thishost/otherpath$1 [P]</td>
1503 <td>doesn't make sense, not supported</td>
1506 <td>^localpath(.*) http://otherhost/otherpath$1</td>
1507 <td>http://otherhost/otherpath/pathinfo via external redirection</td>
1510 <td>^localpath(.*) http://otherhost/otherpath$1 [R]</td>
1511 <td>http://otherhost/otherpath/pathinfo via external redirection (the [R] flag is redundant)</td>
1514 <td>^localpath(.*) http://otherhost/otherpath$1 [P]</td>
1515 <td>http://otherhost/otherpath/pathinfo via internal proxy</td>
1522 <div class="bottomlang">
1523 <p><span>Available Languages: </span><a href="../en/mod/mod_rewrite.html" title="English"> en </a> |
1524 <a href="../fr/mod/mod_rewrite.html" hreflang="fr" rel="alternate" title="Français"> fr </a></p>
1525 </div><div class="top"><a href="#page-header"><img src="../images/up.gif" alt="top" /></a></div><div class="section"><h2><a id="comments_section" name="comments_section">Comments</a></h2><div class="warning"><strong>Notice:</strong><br />This is not a Q&A section. Comments placed here should be pointed towards suggestions on improving the documentation or server, and may be removed again by our moderators if they are either implemented or considered invalid/off-topic. Questions on how to manage the Apache HTTP Server should be directed at either our IRC channel, #httpd, on Freenode, or sent to our <a href="http://httpd.apache.org/lists.html">mailing lists</a>.</div>
1526 <script type="text/javascript"><!--//--><![CDATA[//><!--
1527 var comments_shortname = 'httpd';
1528 var comments_identifier = 'http://httpd.apache.org/docs/trunk/mod/mod_rewrite.html';
1530 if (w.location.hostname.toLowerCase() == "httpd.apache.org") {
1531 d.write('<div id="comments_thread"><\/div>');
1532 var s = d.createElement('script');
1533 s.type = 'text/javascript';
1535 s.src = 'https://comments.apache.org/show_comments.lua?site=' + comments_shortname + '&page=' + comments_identifier;
1536 (d.getElementsByTagName('head')[0] || d.getElementsByTagName('body')[0]).appendChild(s);
1539 d.write('<div id="comments_thread">Comments are disabled for this page at the moment.<\/div>');
1541 })(window, document);
1542 //--><!]]></script></div><div id="footer">
1543 <p class="apache">Copyright 2016 The Apache Software Foundation.<br />Licensed under the <a href="http://www.apache.org/licenses/LICENSE-2.0">Apache License, Version 2.0</a>.</p>
1544 <p class="menu"><a href="../mod/">Modules</a> | <a href="../mod/quickreference.html">Directives</a> | <a href="http://wiki.apache.org/httpd/FAQ">FAQ</a> | <a href="../glossary.html">Glossary</a> | <a href="../sitemap.html">Sitemap</a></p></div><script type="text/javascript"><!--//--><![CDATA[//><!--
1545 if (typeof(prettyPrint) !== 'undefined') {