Gecko [ v3.cesa.co.za ]

Name	Size	Permission	Date
core.html	337.67 KB	-rw-r--r--	2026-06-12 05:08
directive-dict.html	20.46 KB	-rw-r--r--	2026-06-12 05:08
directives.html	58.19 KB	-rw-r--r--	2026-06-12 05:08
event.html	28.64 KB	-rw-r--r--	2026-06-12 05:08
index.html	24.98 KB	-rw-r--r--	2026-06-12 05:08
mod_access_compat.html	28.27 KB	-rw-r--r--	2026-06-12 05:08
mod_actions.html	12.61 KB	-rw-r--r--	2026-06-12 05:08
mod_alias.html	43.79 KB	-rw-r--r--	2026-06-12 05:08
mod_allowmethods.html	7.79 KB	-rw-r--r--	2026-06-12 05:08
mod_asis.html	8.65 KB	-rw-r--r--	2026-06-12 05:08
mod_auth_basic.html	19.39 KB	-rw-r--r--	2026-06-12 05:08
mod_auth_digest.html	20.06 KB	-rw-r--r--	2026-06-12 05:08
mod_auth_form.html	50.26 KB	-rw-r--r--	2026-06-12 05:08
mod_authn_anon.html	16.37 KB	-rw-r--r--	2026-06-12 05:08
mod_authn_core.html	16.45 KB	-rw-r--r--	2026-06-12 05:08
mod_authn_dbd.html	15.01 KB	-rw-r--r--	2026-06-12 05:08
mod_authn_dbm.html	12.48 KB	-rw-r--r--	2026-06-12 05:08
mod_authn_file.html	11.17 KB	-rw-r--r--	2026-06-12 05:08
mod_authn_socache.html	18.79 KB	-rw-r--r--	2026-06-12 05:08
mod_authnz_fcgi.html	26.93 KB	-rw-r--r--	2026-06-12 05:08
mod_authnz_ldap.html	86.06 KB	-rw-r--r--	2026-06-12 05:08
mod_authz_core.html	39.59 KB	-rw-r--r--	2026-06-12 05:08
mod_authz_dbd.html	18.13 KB	-rw-r--r--	2026-06-12 05:08
mod_authz_dbm.html	12.7 KB	-rw-r--r--	2026-06-12 05:08
mod_authz_groupfile.html	10.24 KB	-rw-r--r--	2026-06-12 05:08
mod_authz_host.html	13.12 KB	-rw-r--r--	2026-06-12 05:08
mod_authz_owner.html	11 KB	-rw-r--r--	2026-06-12 05:08
mod_authz_user.html	7.91 KB	-rw-r--r--	2026-06-12 05:08
mod_autoindex.html	70.35 KB	-rw-r--r--	2026-06-12 05:08
mod_brotli.html	22.65 KB	-rw-r--r--	2026-06-12 05:08
mod_buffer.html	8.76 KB	-rw-r--r--	2026-06-12 05:08
mod_cache.html	69.74 KB	-rw-r--r--	2026-06-12 05:08
mod_cache_disk.html	20.06 KB	-rw-r--r--	2026-06-12 05:08
mod_cache_socache.html	18.21 KB	-rw-r--r--	2026-06-12 05:08
mod_cern_meta.html	10.83 KB	-rw-r--r--	2026-06-12 05:08
mod_cgi.html	19.94 KB	-rw-r--r--	2026-06-12 05:08
mod_cgid.html	11.36 KB	-rw-r--r--	2026-06-12 05:08
mod_charset_lite.html	15.11 KB	-rw-r--r--	2026-06-12 05:08
mod_data.html	7.2 KB	-rw-r--r--	2026-06-12 05:08
mod_dav.html	19.88 KB	-rw-r--r--	2026-06-12 05:08
mod_dav_fs.html	10.54 KB	-rw-r--r--	2026-06-12 05:08
mod_dav_lock.html	9.51 KB	-rw-r--r--	2026-06-12 05:08
mod_dbd.html	24.89 KB	-rw-r--r--	2026-06-12 05:08
mod_deflate.html	31.15 KB	-rw-r--r--	2026-06-12 05:08
mod_dialup.html	7.2 KB	-rw-r--r--	2026-06-12 05:08
mod_dir.html	24.83 KB	-rw-r--r--	2026-06-12 05:08
mod_dumpio.html	9.41 KB	-rw-r--r--	2026-06-12 05:08
mod_echo.html	7.16 KB	-rw-r--r--	2026-06-12 05:08
mod_env.html	11.84 KB	-rw-r--r--	2026-06-12 05:08
mod_example_hooks.html	11.01 KB	-rw-r--r--	2026-06-12 05:08
mod_expires.html	17.21 KB	-rw-r--r--	2026-06-12 05:08
mod_ext_filter.html	18.05 KB	-rw-r--r--	2026-06-12 05:08
mod_file_cache.html	15.2 KB	-rw-r--r--	2026-06-12 05:08
mod_filter.html	33.35 KB	-rw-r--r--	2026-06-12 05:08
mod_headers.html	34.06 KB	-rw-r--r--	2026-06-12 05:08
mod_heartbeat.html	9.29 KB	-rw-r--r--	2026-06-12 05:08
mod_heartmonitor.html	11.92 KB	-rw-r--r--	2026-06-12 05:08
mod_http2.html	75.84 KB	-rw-r--r--	2026-06-12 05:08
mod_ident.html	9.74 KB	-rw-r--r--	2026-06-12 05:08
mod_imagemap.html	21.06 KB	-rw-r--r--	2026-06-12 05:08
mod_include.html	59.69 KB	-rw-r--r--	2026-06-12 05:08
mod_info.html	14.52 KB	-rw-r--r--	2026-06-12 05:08
mod_isapi.html	23.44 KB	-rw-r--r--	2026-06-12 05:08
mod_lbmethod_bybusyness.html	7.6 KB	-rw-r--r--	2026-06-12 05:08
mod_lbmethod_byrequests.html	12.3 KB	-rw-r--r--	2026-06-12 05:08
mod_lbmethod_bytraffic.html	7.95 KB	-rw-r--r--	2026-06-12 05:08
mod_lbmethod_heartbeat.html	8.02 KB	-rw-r--r--	2026-06-12 05:08
mod_ldap.html	50.89 KB	-rw-r--r--	2026-06-12 05:08
mod_log_config.html	40.02 KB	-rw-r--r--	2026-06-12 05:08
mod_log_debug.html	9.95 KB	-rw-r--r--	2026-06-12 05:08
mod_log_forensic.html	13.8 KB	-rw-r--r--	2026-06-12 05:08
mod_logio.html	10.98 KB	-rw-r--r--	2026-06-12 05:08
mod_lua.html	93.06 KB	-rw-r--r--	2026-06-12 05:08
mod_macro.html	15.29 KB	-rw-r--r--	2026-06-12 05:08
mod_md.html	109.91 KB	-rw-r--r--	2026-06-12 05:08
mod_mime.html	66.05 KB	-rw-r--r--	2026-06-12 05:08
mod_mime_magic.html	16.52 KB	-rw-r--r--	2026-06-12 05:08
mod_negotiation.html	21.68 KB	-rw-r--r--	2026-06-12 05:08
mod_nw_ssl.html	9.27 KB	-rw-r--r--	2026-06-12 05:08
mod_privileges.html	29.36 KB	-rw-r--r--	2026-06-12 05:08
mod_proxy.html	137.06 KB	-rw-r--r--	2026-06-12 05:08
mod_proxy_ajp.html	32.56 KB	-rw-r--r--	2026-06-12 05:08
mod_proxy_balancer.html	23.03 KB	-rw-r--r--	2026-06-12 05:08
mod_proxy_connect.html	9.85 KB	-rw-r--r--	2026-06-12 05:08
mod_proxy_express.html	13.19 KB	-rw-r--r--	2026-06-12 05:08
mod_proxy_fcgi.html	22.14 KB	-rw-r--r--	2026-06-12 05:08
mod_proxy_fdpass.html	7.2 KB	-rw-r--r--	2026-06-12 05:08
mod_proxy_ftp.html	18.84 KB	-rw-r--r--	2026-06-12 05:08
mod_proxy_hcheck.html	17.43 KB	-rw-r--r--	2026-06-12 05:08
mod_proxy_html.html	34.16 KB	-rw-r--r--	2026-06-12 05:08
mod_proxy_http.html	11.63 KB	-rw-r--r--	2026-06-12 05:08
mod_proxy_http2.html	10.05 KB	-rw-r--r--	2026-06-12 05:08
mod_proxy_scgi.html	14.49 KB	-rw-r--r--	2026-06-12 05:08
mod_proxy_uwsgi.html	8.15 KB	-rw-r--r--	2026-06-12 05:08
mod_proxy_wstunnel.html	10.73 KB	-rw-r--r--	2026-06-12 05:08
mod_ratelimit.html	6.72 KB	-rw-r--r--	2026-06-12 05:08
mod_reflector.html	8.28 KB	-rw-r--r--	2026-06-12 05:08
mod_remoteip.html	26.54 KB	-rw-r--r--	2026-06-12 05:08
mod_reqtimeout.html	12.49 KB	-rw-r--r--	2026-06-12 05:08
mod_request.html	9.93 KB	-rw-r--r--	2026-06-12 05:08
mod_rewrite.html	82.27 KB	-rw-r--r--	2026-06-12 05:08
mod_sed.html	11.53 KB	-rw-r--r--	2026-06-12 05:08
mod_session.html	35.31 KB	-rw-r--r--	2026-06-12 05:08
mod_session_cookie.html	13.55 KB	-rw-r--r--	2026-06-12 05:08
mod_session_crypto.html	17.73 KB	-rw-r--r--	2026-06-12 05:08
mod_session_dbd.html	25.2 KB	-rw-r--r--	2026-06-12 05:08
mod_setenvif.html	23.09 KB	-rw-r--r--	2026-06-12 05:08
mod_slotmem_plain.html	7.76 KB	-rw-r--r--	2026-06-12 05:08
mod_slotmem_shm.html	8.36 KB	-rw-r--r--	2026-06-12 05:08
mod_so.html	15.71 KB	-rw-r--r--	2026-06-12 05:08
mod_socache_dbm.html	5.82 KB	-rw-r--r--	2026-06-12 05:08
mod_socache_dc.html	5.87 KB	-rw-r--r--	2026-06-12 05:08
mod_socache_memcache.html	8.34 KB	-rw-r--r--	2026-06-12 05:08
mod_socache_redis.html	10 KB	-rw-r--r--	2026-06-12 05:08
mod_socache_shmcb.html	5.9 KB	-rw-r--r--	2026-06-12 05:08
mod_speling.html	12.64 KB	-rw-r--r--	2026-06-12 05:08
mod_ssl.html	200.72 KB	-rw-r--r--	2026-06-12 05:08
mod_status.html	13.11 KB	-rw-r--r--	2026-06-12 05:08
mod_substitute.html	14.37 KB	-rw-r--r--	2026-06-12 05:08
mod_suexec.html	8.26 KB	-rw-r--r--	2026-06-12 05:08
mod_systemd.html	7.57 KB	-rw-r--r--	2026-06-12 05:08
mod_unique_id.html	14.89 KB	-rw-r--r--	2026-06-12 05:08
mod_unixd.html	14.69 KB	-rw-r--r--	2026-06-12 05:08
mod_userdir.html	13.57 KB	-rw-r--r--	2026-06-12 05:08
mod_usertrack.html	19.68 KB	-rw-r--r--	2026-06-12 05:08
mod_version.html	10.05 KB	-rw-r--r--	2026-06-12 05:08
mod_vhost_alias.html	22.43 KB	-rw-r--r--	2026-06-12 05:08
mod_watchdog.html	7.73 KB	-rw-r--r--	2026-06-12 05:08
mod_xml2enc.html	15.3 KB	-rw-r--r--	2026-06-12 05:08
module-dict.html	9.77 KB	-rw-r--r--	2026-06-12 05:08
mpm_common.html	75.9 KB	-rw-r--r--	2026-06-12 05:08
mpm_netware.html	9.82 KB	-rw-r--r--	2026-06-12 05:08
mpm_winnt.html	10.58 KB	-rw-r--r--	2026-06-12 05:08
mpmt_os2.html	7.5 KB	-rw-r--r--	2026-06-12 05:08
overrides.html	69.49 KB	-rw-r--r--	2026-06-12 05:08
prefork.html	17.67 KB	-rw-r--r--	2026-06-12 05:08
quickreference.html	199.29 KB	-rw-r--r--	2026-06-12 05:08
worker.html	16.88 KB	-rw-r--r--	2026-06-12 05:08

Rename

<!DOCTYPE html SYSTEM "about:legacy-compat">
<html lang="en"><head><META http-equiv="Content-Type" content="text/html; charset=UTF-8">
<meta content="width=device-width, initial-scale=1" name="viewport">

<title>mod_rewrite - Apache HTTP Server Version 2.4</title>
<link href="../../style/css/manual.css" rel="stylesheet" media="all" type="text/css" title="Main stylesheet">
<link href="../../style/css/manual-loose-100pc.css" rel="alternate stylesheet" media="all" type="text/css" title="No Sidebar - Default font size">
<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">
<script src="../../style/scripts/prettify.min.js">
</script>

The <code class="module"><a href="../mod/mod_rewrite.html">mod_rewrite</a></code> module uses a rule-based rewriting
 engine, based on a PCRE regular-expression parser, to rewrite requested URLs on
 the fly. By default, <code class="module"><a href="../mod/mod_rewrite.html">mod_rewrite</a></code> maps a URL to a filesystem
 path. However, it can also be used to redirect one URL to another URL, or
 to invoke an internal proxy fetch.

<code class="module"><a href="../mod/mod_rewrite.html">mod_rewrite</a></code> provides a flexible and powerful way to
 manipulate URLs using an unlimited number of rules. Each rule can have an
 unlimited number of attached rule conditions, to allow you to rewrite URLs
 based on <a href="#rewritecond">server variables</a> (including HTTP
 headers, connection details, and timestamps), environment variables,
 or other request properties.

<code class="module"><a href="../mod/mod_rewrite.html">mod_rewrite</a></code> can operate on the full URL-path, or any
 portion of it, including the PATH_INFO or QUERY_STRING.

A rewrite rule
 can be invoked in the server configuration files, or in <a class="glossarylink" href="../glossary.html#perdirectory" title="see glossary">per-directory</a> context. The substitution
 string of a rewrite rule can include a query string, and a rule can lead to internal
 sub-processing, external request redirection, or internal proxy
 throughput.

Further details, discussion, and examples, are provided in the
 detailed <a href="../rewrite/index.html">Guide to mod_rewrite</a>.
</div>
<div id="quickview"><h3>Topics</h3>
<ul id="topics">
<li><img alt="" src="../../images/down.gif"> <a href="#logging">Logging</a></li>
</ul><h3 class="directives">Directives</h3>
<ul id="toc">
<li><img alt="" src="../../images/down.gif"> <a href="#rewritebase">RewriteBase</a></li>
<li><img alt="" src="../../images/down.gif"> <a href="#rewritecond">RewriteCond</a></li>
<li><img alt="" src="../../images/down.gif"> <a href="#rewriteengine">RewriteEngine</a></li>
<li><img alt="" src="../../images/down.gif"> <a href="#rewritemap">RewriteMap</a></li>
<li><img alt="" src="../../images/down.gif"> <a href="#rewriteoptions">RewriteOptions</a></li>
<li><img alt="" src="../../images/down.gif"> <a href="#rewriterule">RewriteRule</a></li>
</ul>
<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__&amp;list_id=144532&amp;product=Apache%20httpd-2&amp;query_format=specific&amp;order=changeddate%20DESC%2Cpriority%2Cbug_severity&amp;component=mod_rewrite">Known issues</a></li><li><a href="https://bz.apache.org/bugzilla/enter_bug.cgi?product=Apache%20httpd-2&amp;component=mod_rewrite">Report a bug</a></li></ul></div>
<div class="top"><a href="#page-header"><img alt="top" src="../../images/up.gif"></a></div>
<div class="section">
<h2 id="logging">Logging <a title="Permanent link" href="#logging" class="permalink">&para;</a></h2>

<code class="module"><a href="../mod/mod_rewrite.html">mod_rewrite</a></code> offers detailed logging of its actions
 at the <code>trace1</code> to <code>trace8</code> log levels. The
 log level can be set specifically for <code class="module"><a href="../mod/mod_rewrite.html">mod_rewrite</a></code>
 using the <code class="directive"><a href="../mod/core.html#loglevel">LogLevel</a></code> directive: Up to
 level <code>debug</code>, no actions are logged, while <code>trace8</code>
 means that practically all actions are logged.

<div class="note">
 Using a high trace log level for <code class="module"><a href="../mod/mod_rewrite.html">mod_rewrite</a></code>
 will slow down your Apache HTTP Server dramatically! Use a log
 level higher than <code>trace2</code> only for debugging!
 </div>

<div class="example"><h3>Example</h3><pre class="prettyprint lang-config">LogLevel alert rewrite:trace3</pre>
</div>

<div class="note"><h3>RewriteLog</h3>
 Those familiar with earlier versions of
 <code class="module"><a href="../mod/mod_rewrite.html">mod_rewrite</a></code> will no doubt be looking for the
 <code>RewriteLog</code> and <code>RewriteLogLevel</code>
 directives. Since the release of httpd 2.4, these directives
 have been replaced with the per-module logging configuration
 provided by <code class="directive"><a href="../mod/core.html#loglevel">LogLevel</a></code>.

To get just the <code class="module"><a href="../mod/mod_rewrite.html">mod_rewrite</a></code>-specific log
 messages, pipe the log file through grep:

<div class="example"><pre class="prettyprint lang-sh">tail -f error_log|fgrep '[rewrite:'</pre>
</div>
 </div>

</div>
<div class="top"><a href="#page-header"><img alt="top" src="../../images/up.gif"></a></div>
<div class="directive-section"><h2 id="rewritebase">RewriteBase Directive <a title="Permanent link" href="#rewritebase" class="permalink">&para;</a></h2>
<table class="directive">
<tr><th><a href="directive-dict.html#Description">Description:</a></th><td>Sets the base URL for per-directory rewrites</td></tr>
<tr><th><a href="directive-dict.html#Syntax">Syntax:</a></th><td><code>RewriteBase URL-path</code></td></tr>
<tr><th><a href="directive-dict.html#Default">Default:</a></th><td><code>None</code></td></tr>
<tr><th><a href="directive-dict.html#Context">Context:</a></th><td>directory, .htaccess</td></tr>
<tr><th><a href="directive-dict.html#Override">Override:</a></th><td>FileInfo</td></tr>
<tr><th><a href="directive-dict.html#Status">Status:</a></th><td>Extension</td></tr>
<tr><th><a href="directive-dict.html#Module">Module:</a></th><td>mod_rewrite</td></tr>
</table>
 The <code class="directive">RewriteBase</code> directive specifies the
 URL prefix to be used for
 <a class="glossarylink" href="../glossary.html#perdirectory" title="see glossary">per-directory</a>
 <code class="directive"><a href="#rewriterule">RewriteRule</a></code> directives that
 substitute a relative path.
 This directive is required when you use a relative path
 in a substitution in <a class="glossarylink" href="../glossary.html#perdirectory" title="see glossary">per-directory</a> context unless any
 of the following conditions are true:
 <ul>
 <li> The original request, and the substitution, are underneath the
 <code class="directive"><a href="../mod/core.html#documentroot">DocumentRoot</a></code>
 (as opposed to reachable by other means, such as
 <code class="directive"><a href="../mod/mod_alias.html#alias">Alias</a></code>).</li>
 <li> The directory-path for which the RewriteRule applies, 
 suffixed by the relative substitution, is also valid
 as a URL-path on the server (this is rare).</li>
 <li> In Apache HTTP Server 2.4.16 and later, this directive may be
 omitted when the request is mapped via
 <code class="directive"><a href="../mod/mod_alias.html#alias">Alias</a></code>
 or <code class="module"><a href="../mod/mod_userdir.html">mod_userdir</a></code>.</li>
 </ul>

</div>
<div class="top"><a href="#page-header"><img alt="top" src="../../images/up.gif"></a></div>
<div class="directive-section"><h2 id="rewritecond">RewriteCond Directive <a title="Permanent link" href="#rewritecond" class="permalink">&para;</a></h2>
<table class="directive">
<tr><th><a href="directive-dict.html#Description">Description:</a></th><td>Defines a condition under which rewriting will take place
</td></tr>
<tr><th><a href="directive-dict.html#Syntax">Syntax:</a></th><td><code> RewriteCond
 TestString [!]CondPattern [flags]</code></td></tr>
<tr><th><a href="directive-dict.html#Context">Context:</a></th><td>server config, virtual host, directory, .htaccess</td></tr>
<tr><th><a href="directive-dict.html#Override">Override:</a></th><td>FileInfo</td></tr>
<tr><th><a href="directive-dict.html#Status">Status:</a></th><td>Extension</td></tr>
<tr><th><a href="directive-dict.html#Module">Module:</a></th><td>mod_rewrite</td></tr>
</table>
 The <code class="directive">RewriteCond</code> directive defines a
 rule condition. One or more <code class="directive">RewriteCond</code>
 can precede a <code class="directive"><a href="#rewriterule">RewriteRule</a></code>
 directive. The following rule is then only used if both
 the current state of the URI matches its pattern, and if these conditions are met.

If the CondPattern is prefixed with a <code>!</code> the
 condition is determined to be true only if the the
 CondPattern does not match.

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). $1 to $9 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. $0 provides
 access to the whole string matched by that pattern.

<div class="note">Backreferences are only defined if the pattern
 matches. Thus, if the pattern is prefixed with
 <code>!</code>, no backreferences are ever defined.</div>
 </li>
 <li>
 RewriteCond backreferences: These are
 backreferences of the form <code>%N</code>
 (0 &lt;= N &lt;= 9). %1 to %9 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. %0 provides access to the whole string matched by
 that pattern.

<div class="note">Backreferences are only defined if the pattern
 matches. Thus, if the pattern is prefixed with
 <code>!</code>, no backreferences are ever defined.</div>
 </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:

<table>
 
 <tr>
 <th>HTTP headers:</th> <th>connection &amp; request:</th> <th></th>
 </tr>

<tr>
 <td>
 HTTP_ACCEPT 
 HTTP_COOKIE 
 HTTP_FORWARDED 
 HTTP_HOST 
 HTTP_PROXY_CONNECTION 
 HTTP_REFERER 
 HTTP_USER_AGENT 
 </td>

<td>
 AUTH_TYPE 
 CONN_REMOTE_ADDR 
 CONTEXT_PREFIX 
 CONTEXT_DOCUMENT_ROOT 
 IPV6 
 PATH_INFO 
 QUERY_STRING 
 REMOTE_ADDR 
 REMOTE_HOST 
 REMOTE_IDENT 
 REMOTE_PORT 
 REMOTE_USER 
 REQUEST_METHOD 
 SCRIPT_FILENAME 
 </td>

<tr>
 <th>server internals:</th> <th>date and time:</th> <th>specials:</th>
 </tr>

<tr>
 <td>
 DOCUMENT_ROOT 
 SCRIPT_GROUP 
 SCRIPT_USER 
 SERVER_ADDR 
 SERVER_ADMIN 
 SERVER_NAME 
 SERVER_PORT 
 SERVER_PROTOCOL 
 SERVER_SOFTWARE 
 </td>

<td>
 API_VERSION 
 CONN_REMOTE_ADDR 
 HTTPS 
 IS_SUBREQ 
 REMOTE_ADDR 
 REQUEST_FILENAME 
 REQUEST_SCHEME 
 REQUEST_URI 
 THE_REQUEST 
 </td>
 </tr>
 </table>

These variables all
 correspond to the similarly named HTTP
 MIME-headers, C variables of the Apache HTTP Server or
 <code>struct tm</code> fields of the Unix system.
 Most are documented in the 
 <a href="../expr.html#vars">Expressions doc</a>, in the
 <a href="../env.html">Environment Variables doc</a>,
 or the CGI specification (<a href="https://www.rfc-editor.org/rfc/rfc3875">RFC 3875</a>).

SERVER_NAME and SERVER_PORT depend on the values of
 <code class="directive"><a href="../mod/core.html#usecanonicalname">UseCanonicalName</a></code> and
 <code class="directive"><a href="../mod/core.html#usecanonicalphysicalport">UseCanonicalPhysicalPort</a></code>
 respectively.

Those that are special to <code class="module"><a href="../mod/mod_rewrite.html">mod_rewrite</a></code> include those below.
 <dl>
 <dt><code>API_VERSION</code></dt>

<dd>This is the version of the Apache httpd module API
 (the internal interface between server and
 module) in the current httpd build, as defined in
 include/ap_mmn.h. The module API version
 corresponds to the version of Apache httpd in use (in
 the release version of Apache httpd 1.3.14, for
 instance, it is 19990320:10), but is mainly of
 interest to module authors.</dd>

<dt><code>CONN_REMOTE_ADDR</code></dt>

<dd>Since 2.4.8: The peer IP address of the connection (see the
 <code class="module"><a href="../mod/mod_remoteip.html">mod_remoteip</a></code> module).</dd>

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

<dd>Will contain the text "on" if the connection is
 using SSL/TLS, or "off" otherwise. (This variable
 can be safely used regardless of whether or not
 <code class="module"><a href="../mod/mod_ssl.html">mod_ssl</a></code> is loaded).</dd>

<dt><code>IS_SUBREQ</code></dt>

<dd>Will contain the text "true" if the request
 currently being processed is a sub-request,
 "false" otherwise. Sub-requests may be generated
 by modules that need to resolve additional files
 or URIs in order to complete their tasks.</dd>

<dt><code>REMOTE_ADDR</code></dt>

<dd>The IP address of the remote host (see the
 <code class="module"><a href="../mod/mod_remoteip.html">mod_remoteip</a></code> module).</dd>

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

<dd>The full local filesystem path to the file or
 script matching the request, if this has already
 been determined by the server at the time
 <code>REQUEST_FILENAME</code> is referenced. Otherwise,
 such as when used in virtual host context, the same
 value as <code>REQUEST_URI</code>. Depending on the value of
 <code class="directive"><a href="../mod/core.html#acceptpathinfo">AcceptPathInfo</a></code>, the
 server may have only used some leading components of the
 <code>REQUEST_URI</code> to map the request to a file.
 </dd>

<dt><code>REQUEST_SCHEME</code></dt>

<dd>Will contain the scheme of the request (usually
 "http" or "https"). This value can be influenced with
 <code class="directive"><a href="../mod/core.html#servername">ServerName</a></code>.</dd>

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

<dd>The path component of the requested URI,
 such as "/index.html". This notably excludes the
 query string which is available as its own variable
 named <code>QUERY_STRING</code>. The value returned for
 <code>REQUEST_URI</code> 
 has already been %-decoded, to re-encode it pass it through
 the "escape" <a href="#mapfunc">mapping-function</a>.
 Note that this server variable differs from the CGI
 environment variable of the same name: in a CGI context,
 <code>REQUEST_URI</code> contains the full original URI
 from the request line, including the query string. See
 the <code class="directive"><a href="../mod/core.html#cgivar">CGIVar</a></code>
 directive for details.
 </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. This value has not been unescaped
 (decoded), unlike most other variables below.</dd>

</dl>
 </li>
 </ul>

If the TestString has the special value <code>expr</code>,
 the CondPattern will be treated as an
 <a href="../expr.html">ap_expr</a>. HTTP headers referenced in the
 expression will be added to the Vary header if the <code>novary</code>
 flag is not given.

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 HTTP 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>).
 If a substitution occurred and the rewriting continues,
 the value of both variables will be updated accordingly.
 If used in per-server context (i.e., before the
 request is mapped to the filesystem) SCRIPT_FILENAME and
 REQUEST_FILENAME cannot contain the full local filesystem
 path since the path is unknown at this stage of processing.
 Both variables will initially contain the value of REQUEST_URI
 in that case. In order to obtain the full local filesystem
 path of the request in per-server context, use an URL-based
 look-ahead <code>%{LA-U:REQUEST_FILENAME}</code> to determine
 the final value of REQUEST_FILENAME.</li>

<li>
 <code>%{ENV:variable}</code>, where variable can be
 any environment variable, is also available.
 This is looked-up via internal
 Apache httpd structures and (if not found there) via
 <code>getenv()</code> from the Apache httpd server process.</li>

<li>
 <code>%{SSL:variable}</code>, where variable is the
 name of an <a href="mod_ssl.html#envvars">SSL environment
 variable</a>, can be used whether or not
 <code class="module"><a href="../mod/mod_ssl.html">mod_ssl</a></code> is loaded, but will always expand to
 the empty string if it is not. Example:
 <code>%{SSL:SSL_CIPHER_USEKEYSIZE}</code> may expand to
 <code>128</code>. These variables are available even without
 setting the <code>StdEnvVars</code> option of the
 <code class="directive"><a href="../mod/mod_ssl.html#ssloptions">SSLOptions</a></code> directive.</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>''.
 If a HTTP header is used in a condition this header is added to
 the Vary header of the response in case the condition evaluates
 to true for the request. It is not added if the
 condition evaluates to false for the request. Adding the HTTP header
 to the Vary header of the response is needed for proper caching.
 It has to be kept in mind that conditions follow a short circuit
 logic in the case of the '<code>ornext|OR</code>' flag
 so that certain conditions might not be evaluated at all.</li>

<li>
 <a id="LA-U" name="LA-U"><code>%{LA-U:variable}</code></a>
 can be used for look-aheads which perform
 an internal (URL-based) sub-request to determine the final
 value of variable. This can be used to access
 variable for rewriting which is not available at the current
 stage, but will be set in a later phase.
 For instance, to rewrite according to the
 <code>REMOTE_USER</code> variable from within the
 per-server context (<code>apache2.conf</code> file) you must
 use <code>%{LA-U:REMOTE_USER}</code> - this
 variable is set by the authorization phases, which come
 after the URL translation phase (during which
 <code class="module"><a href="../mod/mod_rewrite.html">mod_rewrite</a></code> operates).
 On the other hand, because <code class="module"><a href="../mod/mod_rewrite.html">mod_rewrite</a></code> implements
 its <a class="glossarylink" href="../glossary.html#perdirectory" title="see glossary">per-directory</a> context via
 the Fixup phase of the API and because the authorization
 phases come before this phase, you just can use
 <code>%{REMOTE_USER}</code> in that context.</li>

<li>
 <code>%{LA-F:variable}</code> can be used to perform an internal
 (filename-based) sub-request, to determine the final value
 of variable. Most of the time, this is the same as
 LA-U above.</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.

CondPattern is usually a
 <a class="glossarylink" href="../glossary.html#regex" title="see glossary">regular expression</a>, but there is
 additional syntax available to perform other useful tests against
 the Teststring:

<ol>
 <li>You can prefix the pattern string with a
 '<code>!</code>' character (exclamation mark) to negate the result
 of the condition, no matter what kind of CondPattern is used.
 </li>

<li>
 You can perform lexicographical string comparisons:

<dl>
 <dt>&lt;CondPattern</dt>
 <dd>Lexicographically precedes 
 Treats the CondPattern as a plain string and
 compares it lexicographically to TestString. True if
 TestString lexicographically precedes
 CondPattern.</dd>

<dt>&gt;CondPattern</dt>
 <dd>Lexicographically follows 
 Treats the CondPattern as a plain string and
 compares it lexicographically to TestString. True if
 TestString lexicographically follows
 CondPattern.</dd>

<dt>=CondPattern</dt>
 <dd>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.</dd>

<dt>&lt;=CondPattern</dt>
 <dd>Lexicographically less than or equal to 
 Treats the CondPattern as a plain string and
 compares it lexicographically to TestString. True
 if TestString lexicographically precedes
 CondPattern, or is equal to CondPattern
 (the two strings are equal, character for character).</dd>

<dt>&gt;=CondPattern</dt>
 <dd>Lexicographically greater than or equal to 
 Treats the CondPattern as a plain string and
 compares it lexicographically to TestString. True
 if TestString lexicographically follows
 CondPattern, or is equal to CondPattern
 (the two strings are equal, character for character).</dd>
 </dl>
 <div class="note"><h3>Note</h3>
 The string comparison operator is part of the CondPattern
 argument and must be included in the quotes if those are used. Eg.
 
 <pre class="prettyprint lang-config">RewriteCond %{HTTP_USER_AGENT} "=This Robot/1.0"</pre>

</div>
 
 </li>

<li>
 You can perform integer comparisons:
 <dl>

<dt>-eq</dt>
 <dd>Is numerically equal to 
 The TestString is treated as an integer, and is
 numerically compared to the CondPattern. True if
 the two are numerically equal.</dd>

<dt>-ge</dt>
 <dd>Is numerically greater than or equal to 
 The TestString is treated as an integer, and is
 numerically compared to the CondPattern. True if
 the TestString is numerically greater than or equal
 to the CondPattern.</dd>

<dt>-gt</dt>
 <dd>Is numerically greater than 
 The TestString is treated as an integer, and is
 numerically compared to the CondPattern. True if
 the TestString is numerically greater than
 the CondPattern.</dd>

<dt>-le</dt>
 <dd>Is numerically less than or equal to 
 The TestString is treated as an integer, and is
 numerically compared to the CondPattern. True if
 the TestString is numerically less than or equal
 to the CondPattern. Avoid confusion with the
 -l by using the -L or
 -h variant.</dd>

<dt>-lt</dt>
 <dd>Is numerically less than 
 The TestString is treated as an integer, and is
 numerically compared to the CondPattern. True if
 the TestString is numerically less than
 the CondPattern. Avoid confusion with the
 -l by using the -L or
 -h variant.</dd>

<dt>-ne</dt>
 <dd>Is numerically not equal to 
 The TestString is treated as an integer, and is
 numerically compared to the CondPattern. True if
 the two are numerically different. This is equivalent to
 <code>!-eq</code>.</dd>

</dl>
 </li>

<li>You can perform various file attribute tests:

<dl>

<dd>Is directory. 
 Treats the TestString as a pathname and tests
 whether or not it exists, and is a directory.
 </dd>

<dd>Is regular file.

Treats the TestString as a pathname and tests
 whether or not it exists, and is a regular file.
 </dd>

<dd>Is existing file, via subrequest. 
 Checks whether or not TestString is a valid file,
 accessible via all the server's currently-configured
 access controls for that path. This uses an internal
 subrequest to do the check, so use it with care -
 it can impact your server's performance!
 </dd>

<dt>-h</dt>
 <dd>Is symbolic link, bash convention. 
 See -l.
 </dd>

<dd>Is symbolic link. 
 Treats the TestString as a pathname and tests
 whether or not it exists, and is a symbolic link. May also
 use the bash convention of -L or
 -h if there's a possibility of confusion
 such as when using the -lt or
 -le tests.
 </dd>

<dt>-L</dt>
 <dd>Is symbolic link, bash convention. 
 See -l.</dd>

<dt>-s</dt>
 <dd>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.</dd>

<dt>-U</dt>
 <dd>Is existing URL, via subrequest. 
 Checks whether or not TestString is a valid URL,
 accessible via all the server's currently-configured
 access controls for that path. This uses an internal
 subrequest to do the check, so use it with care -
 it can impact your server's performance!
 This flag only returns information about things
 like access control, authentication, and authorization. This flag
 does not return information about the status code the
 configured handler (static file, CGI, proxy, etc.) would have
 returned. </dd>

<dt>-x</dt>
 <dd>Has executable permissions. 
 Treats the TestString as a pathname and tests
 whether or not it exists, and has executable permissions.
 These permissions are determined according to
 the underlying OS.</dd>

</dl>

For example:

<pre class="prettyprint lang-config">RewriteCond /var/www/%{REQUEST_URI} !-f
RewriteRule ^(.+) /other/archive/$1 [R]</pre>

</li>

<li>
 If the TestString has the special value <code>expr</code>, the
 CondPattern will be treated as an
 <a href="../expr.html">ap_expr</a>.

In the below example, <code>-strmatch</code> is used to
 compare the <code>REFERER</code> against the site hostname,
 to block unwanted hotlinking.

<pre class="prettyprint lang-config">RewriteCond expr "! %{HTTP_REFERER} -strmatch '*://%{HTTP_HOST}/*'"
RewriteRule "^/images" "-" [F]</pre>

</li>
 </ol>

You can also set special flags for CondPattern by appending
 <code>[</code>flags<code>]</code>
 as the third argument to the <code class="directive">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 filesystem 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:

<pre class="prettyprint lang-config">RewriteCond "%{REMOTE_HOST}" "^host1" [OR]
RewriteCond "%{REMOTE_HOST}" "^host2" [OR]
RewriteCond "%{REMOTE_HOST}" "^host3"
RewriteRule ...some special stuff for any of these hosts...</pre>

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

<li>'<code>novary|NV</code>'
 (no vary) 
 If a HTTP header is used in the condition, this flag prevents
 this header from being added to the Vary header of the response. 
 Using this flag might break proper caching of the response if
 the representation of this response varies on the value of this header.
 So this flag should be only used if the meaning of the Vary header
 is well understood.
 </li>
 </ul>

Example:

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

<pre class="prettyprint lang-config">RewriteCond "%{HTTP_USER_AGENT}" "(iPhone|Blackberry|Android)"
RewriteRule "^/$" "/homepage.mobile.html" [L]

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

Explanation: If you use a browser which identifies itself
 as a mobile browser (note that the example is incomplete, as
 there are many other mobile platforms), the mobile version of
 the homepage is served. Otherwise, the standard page is served.

By default, multiple <code class="directive">RewriteCond</code>s
 are evaluated in sequence with an implied logical AND.
 If a condition fails, in the absence of an
 <code>OR</code> flag, the entire ruleset is abandoned,
 and further conditions are not evaluated.

</div>
<div class="top"><a href="#page-header"><img alt="top" src="../../images/up.gif"></a></div>
<div class="directive-section"><h2 id="rewriteengine">RewriteEngine Directive <a title="Permanent link" href="#rewriteengine" class="permalink">&para;</a></h2>
<table class="directive">
<tr><th><a href="directive-dict.html#Description">Description:</a></th><td>Enables or disables runtime rewriting engine</td></tr>
<tr><th><a href="directive-dict.html#Syntax">Syntax:</a></th><td><code>RewriteEngine on|off</code></td></tr>
<tr><th><a href="directive-dict.html#Default">Default:</a></th><td><code>RewriteEngine off</code></td></tr>
<tr><th><a href="directive-dict.html#Context">Context:</a></th><td>server config, virtual host, directory, .htaccess</td></tr>
<tr><th><a href="directive-dict.html#Override">Override:</a></th><td>FileInfo</td></tr>
<tr><th><a href="directive-dict.html#Status">Status:</a></th><td>Extension</td></tr>
<tr><th><a href="directive-dict.html#Module">Module:</a></th><td>mod_rewrite</td></tr>
</table>

The <code class="directive">RewriteEngine</code> directive enables or
 disables the runtime rewriting engine. If it is set to
 <code>off</code> this module does no runtime processing at
 all. It does not even update the <code>SCRIPT_URx</code>
 environment variables.

Use this directive to disable rules in a particular context,
 rather than commenting out all the <code class="directive"><a href="#rewriterule">RewriteRule</a></code> directives.

Note that rewrite configurations are not
 inherited by virtual hosts. This means that you need to have a
 <code>RewriteEngine on</code> directive for each virtual host
 in which you wish to use rewrite rules.

<code class="directive"><a href="#rewritemap">RewriteMap</a></code> directives
 of the type <code>prg</code>
 are not started during server initialization if they're defined in a
 context that does not have <code class="directive">RewriteEngine</code> set to
 <code>on</code>

</div>
<div class="top"><a href="#page-header"><img alt="top" src="../../images/up.gif"></a></div>
<div class="directive-section"><h2 id="rewritemap">RewriteMap Directive <a title="Permanent link" href="#rewritemap" class="permalink">&para;</a></h2>
<table class="directive">
<tr><th><a href="directive-dict.html#Description">Description:</a></th><td>Defines a mapping function for key-lookup</td></tr>
<tr><th><a href="directive-dict.html#Syntax">Syntax:</a></th><td><code>RewriteMap MapName MapType:MapSource
 [MapTypeOptions]
</code></td></tr>
<tr><th><a href="directive-dict.html#Context">Context:</a></th><td>server config, virtual host</td></tr>
<tr><th><a href="directive-dict.html#Status">Status:</a></th><td>Extension</td></tr>
<tr><th><a href="directive-dict.html#Module">Module:</a></th><td>mod_rewrite</td></tr>
<tr><th><a href="directive-dict.html#Compatibility">Compatibility:</a></th><td>The 3rd parameter, MapTypeOptions, is only available in Apache httpd
2.4.29 and later.</td></tr>
</table>
 The <code class="directive">RewriteMap</code> directive defines a
 Rewriting Map which can be used inside rule
 substitution strings by the mapping-functions to
 insert/substitute fields through a key lookup. The source of
 this lookup can be of various types.

The <a id="mapfunc" name="mapfunc">MapName</a> is
 the name of the map and will be used to specify a
 mapping-function for the substitution strings of a rewriting
 rule via one of the following constructs:

<code>${</code> MapName <code>:</code>
 LookupKey <code>}</code> 
 <code>${</code> MapName <code>:</code>
 LookupKey <code>|</code> DefaultValue
 <code>}</code>

When such a construct occurs, the map MapName is
 consulted and the key LookupKey is looked-up. If the
 key is found, the map-function construct is substituted by
 SubstValue. If the key is not found then it is
 substituted by DefaultValue or by the empty string
 if no DefaultValue was specified. Empty values
 behave as if the key was absent, therefore it is not possible
 to distinguish between empty-valued keys and absent keys.

For example, you might define a
 <code class="directive">RewriteMap</code> as:

<pre class="prettyprint lang-config">RewriteMap examplemap "txt:/path/to/file/map.txt"</pre>

You would then be able to use this map in a
 <code class="directive"><a href="#rewriterule">RewriteRule</a></code> as follows:

<pre class="prettyprint lang-config">RewriteRule "^/ex/(.*)" "${examplemap:$1}"</pre>

The meaning of the MapTypeOptions argument depends on
 particular MapType. See the
 <a href="../rewrite/rewritemap.html">Using RewriteMap</a> for
 more information.

The following combinations for MapType and
 MapSource can be used:

<dl>

<dt>txt</dt>
 <dd>A plain text file containing space-separated key-value
 pairs, one per line. (<a href="../rewrite/rewritemap.html#txt">Details ...</a>)</dd>

<dt>rnd</dt>
 <dd>Randomly selects an entry from a plain text file (<a href="../rewrite/rewritemap.html#rnd">Details ...</a>)</dd>

<dt>dbm</dt>
 <dd>Looks up an entry in a dbm file containing name, value
 pairs. Hash is constructed from a plain text file format using
 the <code><a href="../programs/httxt2dbm.html">httxt2dbm</a></code>
 utility. (<a href="../rewrite/rewritemap.html#dbm">Details ...</a>)</dd>

<dt>int</dt>
 <dd>One of the four available internal functions provided by
 <code>RewriteMap</code>: toupper, tolower, escape or
 unescape. (<a href="../rewrite/rewritemap.html#int">Details ...</a>)</dd>

<dt>prg</dt>
 <dd>Calls an external program or script to process the
 rewriting. (<a href="../rewrite/rewritemap.html#prg">Details ...</a>)</dd>

<dt>dbd or fastdbd</dt>
 <dd>A SQL SELECT statement to be performed to look up the
 rewrite target. (<a href="../rewrite/rewritemap.html#dbd">Details ...</a>)</dd>
 </dl>

Further details, and numerous examples, may be found in the <a href="../rewrite/rewritemap.html">RewriteMap HowTo</a>

</div>
<div class="top"><a href="#page-header"><img alt="top" src="../../images/up.gif"></a></div>
<div class="directive-section"><h2 id="rewriteoptions">RewriteOptions Directive <a title="Permanent link" href="#rewriteoptions" class="permalink">&para;</a></h2>
<table class="directive">
<tr><th><a href="directive-dict.html#Description">Description:</a></th><td>Sets some special options for the rewrite engine</td></tr>
<tr><th><a href="directive-dict.html#Syntax">Syntax:</a></th><td><code>RewriteOptions <var>Options</var></code></td></tr>
<tr><th><a href="directive-dict.html#Context">Context:</a></th><td>server config, virtual host, directory, .htaccess</td></tr>
<tr><th><a href="directive-dict.html#Override">Override:</a></th><td>FileInfo</td></tr>
<tr><th><a href="directive-dict.html#Status">Status:</a></th><td>Extension</td></tr>
<tr><th><a href="directive-dict.html#Module">Module:</a></th><td>mod_rewrite</td></tr>
</table>

The <code class="directive">RewriteOptions</code> directive sets some
 special options for the current per-server or per-directory
 configuration. The Option string can currently
 only be one of the following:

<dl>
 <dt><code>Inherit</code></dt>
 <dd>

This forces the current configuration to inherit the
 configuration of the parent. In per-virtual-server context,
 this means that the maps, conditions and rules of the main
 server are inherited. In per-directory context this means
 that conditions and rules of the parent directory's
 <code>.htaccess</code> configuration or
 <code class="directive"><a href="../mod/core.html#directory">&lt;Directory&gt;</a></code>
 sections are inherited. The inherited rules are virtually copied
 to the section where this directive is being used. If used in
 combination with local rules, the inherited rules are copied behind
 the local rules. The position of this directive - below or above
 of local rules - has no influence on this behavior. If local
 rules forced the rewriting to stop, the inherited rules won't
 be processed.

<div class="warning">
 Rules inherited from the parent scope are applied
 after rules specified in the child scope.
 </div>
 </dd>

<dt><code>InheritBefore</code></dt>
 <dd>
 Like <code>Inherit</code> above, but the rules from the parent scope
 are applied before rules specified in the child scope. 
 Available in Apache HTTP Server 2.3.10 and later.
 </dd>

<dt><code>InheritDown</code></dt>
 <dd>

If this option is enabled, all child configurations will inherit
 the configuration of the current configuration. It is equivalent to
 specifying <code>RewriteOptions Inherit</code> in all child
 configurations. See the <code>Inherit</code> option for more details
 on how the parent-child relationships are handled. 
 Available in Apache HTTP Server 2.4.8 and later.
 </dd>

<dt><code>InheritDownBefore</code></dt>
 <dd>

Like <code>InheritDown</code> above, but the rules from the current
 scope are applied before rules specified in any child's
 scope. 
 Available in Apache HTTP Server 2.4.8 and later.
 </dd>

<dt><code>IgnoreInherit</code></dt>
 <dd>

This option forces the current and child configurations to ignore
 all rules that would be inherited from a parent specifying
 <code>InheritDown</code> or <code>InheritDownBefore</code>. 
 Available in Apache HTTP Server 2.4.8 and later.
 </dd>

<dt><code>AllowNoSlash</code></dt>
 <dd>
 By default, <code class="module"><a href="../mod/mod_rewrite.html">mod_rewrite</a></code> will ignore URLs that map to a
 directory on disk but lack a trailing slash, in the expectation that
 the <code class="module"><a href="../mod/mod_dir.html">mod_dir</a></code> module will issue the client with a redirect to
 the canonical URL with a trailing slash.

When the <code class="directive"><a href="../mod/mod_dir.html#directoryslash">DirectorySlash</a></code> directive
 is set to off, the <code>AllowNoSlash</code> option can be enabled to ensure
 that rewrite rules are no longer ignored. This option makes it possible to
 apply rewrite rules within .htaccess files that match the directory without
 a trailing slash, if so desired. 
 Available in Apache HTTP Server 2.4.0 and later.
 </dd>

<dt><code>AllowAnyURI</code></dt>
 <dd>

When <code class="directive"><a href="#rewriterule">RewriteRule</a></code>
 is used in <code>VirtualHost</code> or server context with
 version 2.2.22 or later of httpd, <code class="module"><a href="../mod/mod_rewrite.html">mod_rewrite</a></code>
 will only process the rewrite rules if the request URI is a <a href="directive-dict.html#Syntax">URL-path</a>. This avoids
 some security issues where particular rules could allow
 "surprising" pattern expansions (see <a href="http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2011-3368">CVE-2011-3368</a>
 and <a href="http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2011-4317">CVE-2011-4317</a>).
 To lift the restriction on matching a URL-path, the
 <code>AllowAnyURI</code> option can be enabled, and
 <code class="module"><a href="../mod/mod_rewrite.html">mod_rewrite</a></code> will apply the rule set to any
 request URI string, regardless of whether that string matches
 the URL-path grammar required by the HTTP specification. 
 Available in Apache HTTP Server 2.4.3 and later.

<div class="warning">
 <h3>Security Warning</h3>

Enabling this option will make the server vulnerable to
 security issues if used with rewrite rules which are not
 carefully authored. It is strongly recommended
 that this option is not used. In particular, beware of input
 strings containing the '<code>@</code>' character which could
 change the interpretation of the transformed URI, as per the
 above CVE names.
 </div>
 </dd>

<dt><code>MergeBase</code></dt>
 <dd>

With this option, the value of <code class="directive"><a href="#rewritebase">RewriteBase</a></code> is copied from where it's explicitly defined
 into any sub-directory or sub-location that doesn't define its own
 <code class="directive"><a href="#rewritebase">RewriteBase</a></code>. This was the
 default behavior in 2.4.0 through 2.4.3, and the flag to restore it is
 available Apache HTTP Server 2.4.4 and later.
 </dd>

<dt><code>IgnoreContextInfo</code></dt>
 <dd>

When a relative substitution is made
 in directory (htaccess) context and <code class="directive"><a href="#rewritebase">RewriteBase</a></code> has not been set, this module uses some
 extended URL and filesystem context information to change the
 relative substitution back into a URL. Modules such as
 <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>
 supply this extended context info. Available in 2.4.16 and later.
 </dd>

<dt><code>LegacyPrefixDocRoot</code></dt>
 <dd>

Prior to 2.4.26, if a substitution was an absolute URL that matched
 the current virtual host, the URL might first be reduced to a URL-path
 and then later reduced to a local path. Since the URL can be reduced 
 to a local path, the path should be prefixed with the document root. 
 This prevents a file such as /tmp/myfile from being accessed when a 
 request is made to http://host/file/myfile with the following 
 <code class="directive"><a href="#rewriterule">RewriteRule</a></code>.
 <pre class="prettyprint lang-config">RewriteRule /file/(.*) http://localhost/tmp/$1</pre>

This option allows the old behavior to be used where the document
 root is not prefixed to a local path that was reduced from a 
 URL. Available in 2.4.26 and later.
 </dd>

</dl>

</div>
<div class="top"><a href="#page-header"><img alt="top" src="../../images/up.gif"></a></div>
<div class="directive-section"><h2 id="rewriterule">RewriteRule Directive <a title="Permanent link" href="#rewriterule" class="permalink">&para;</a></h2>
<table class="directive">
<tr><th><a href="directive-dict.html#Description">Description:</a></th><td>Defines rules for the rewriting engine</td></tr>
<tr><th><a href="directive-dict.html#Syntax">Syntax:</a></th><td><code>RewriteRule
 [!]Pattern Substitution [flags]</code></td></tr>
<tr><th><a href="directive-dict.html#Context">Context:</a></th><td>server config, virtual host, directory, .htaccess</td></tr>
<tr><th><a href="directive-dict.html#Override">Override:</a></th><td>FileInfo</td></tr>
<tr><th><a href="directive-dict.html#Status">Status:</a></th><td>Extension</td></tr>
<tr><th><a href="directive-dict.html#Module">Module:</a></th><td>mod_rewrite</td></tr>
</table>
 The <code class="directive">RewriteRule</code> 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.

<a id="patterns" name="patterns">Pattern</a> is
 a <a id="regexp" name="regexp"><a class="glossarylink" href="../glossary.html#regex" title="see glossary">regular
 expression</a></a>. What this pattern is compared against varies depending
 on where the <code class="directive">RewriteRule</code> directive is defined.

If the pattern is prefixed with a <code>!</code> the
 substitution will be performed only if the the
 pattern does not match.

<div class="note"><h3><a id="what_is_matched" name="what_is_matched">What is matched?</a></h3>

<ul>
 <li>In <code class="directive"><a href="../mod/core.html#virtualhost">VirtualHost</a></code> context,
 The Pattern will initially be matched against the part of the
 URL after the hostname and port, and before the query string (e.g. "/app1/index.html").
 This is the (%-decoded) <a href="directive-dict.html#Syntax">URL-path</a>.</li>

<li>In <a class="glossarylink" href="../glossary.html#perdirectory" title="see glossary">per-directory context</a>
 (<code class="directive"><a href="../mod/core.html#directory">Directory</a></code> and .htaccess),
 the Pattern is matched against only a partial path, for example a request
 of "/app1/index.html" may result in comparison against "app1/index.html" 
 or "index.html" depending on the directory-path for which the
 <code class="directive">RewriteRule</code> applies.

The directory-path to which the rule applies is stripped from the currently mapped
 filesystem path before comparison (up to and including a trailing slash). 
 The net result of this <a class="glossarylink" href="../glossary.html#perdirectory" title="see glossary">per-directory</a> prefix stripping is that rules in
 this context only match against the portion of the currently mapped filesystem path 
 "below" the directory-path to which the rule applies.

Directives such as <code class="directive"><a href="../mod/core.html#documentroot">DocumentRoot</a></code> and <code class="directive"><a href="../mod/mod_alias.html#alias">Alias</a></code>, or even the 
 result of previous <code class="directive">RewriteRule</code> substitutions, determine
 the currently mapped filesystem path. 
 
 </li>

<li>If you wish to match against the hostname, port, or query string, use a
 <code class="directive"><a href="#rewritecond">RewriteCond</a></code> with the
 <code>%{HTTP_HOST}</code>, <code>%{SERVER_PORT}</code>, or
 <code>%{QUERY_STRING}</code> variables respectively.</li>
</ul>
</div>

<div class="note"><h3><a class="glossarylink" href="../glossary.html#perdirectory" title="see glossary">Per-directory</a> Rewrites</h3>
<ul>
<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">&lt;Directory&gt;</a></code> sections, with some additional
complexity.</li>

<li>To enable the rewrite engine in this context, you need to set
<code>RewriteEngine On</code> and
at least one of the <code>FollowSymLinks</code> or
<code>SymLinksIfOwnerMatch</code>
<code class="directive"><a href="../mod/core.html#options">Options</a></code> must be enabled. Note
that these options cannot be set in a distributed configuration file
(<code>.htaccess</code>) unless
<code class="directive"><a href="../mod/core.html#allowoverride">AllowOverride</a></code> permits it
in the server configuration.</li>

<li>See the <code class="directive"><a href="#rewritebase">RewriteBase</a></code>
directive for more information regarding what prefix will be added back to
relative substitutions.</li>

<li> If you wish to match against the full URL-path in a 
<a class="glossarylink" href="../glossary.html#perdirectory" title="see glossary">per-directory</a> context
RewriteRule, use the <code>%{REQUEST_URI}</code> variable in
a <code class="directive"><a href="#rewritecond">RewriteCond</a></code>.</li>

<li>The removed prefix always ends with a slash, meaning the matching occurs against a string which
never has a leading slash. Therefore, a Pattern with <code>^/</code> never
matches in <a class="glossarylink" href="../glossary.html#perdirectory" title="see glossary">per-directory</a> context.</li>

<li>Although rewrite rules are syntactically permitted in <code class="directive"><a href="../mod/core.html#location">&lt;Location&gt;</a></code> and <code class="directive"><a href="../mod/core.html#files">&lt;Files&gt;</a></code> sections
(including their regular expression counterparts), this
should never be necessary and is unsupported. A likely feature
to break in these contexts is relative substitutions.</li>

<li>The <code class="directive"><a href="../mod/core.html#if">If</a></code> blocks
follow the rules of the directory context.</li>

<li>By default, mod_rewrite overrides rules when <a href="../sections.html#merging">
merging sections</a> belonging to the same context. The <code class="directive"><a href="#rewriteoptions">RewriteOptions</a></code> directive can change this behavior,
for example using the Inherit setting.</li>

<li>The <code class="directive"><a href="#rewriteoptions">RewriteOptions</a></code> also regulates the
behavior of sections that are stated at the same nesting level of the configuration. In the
following example, by default only the RewriteRules stated in the second 
<code class="directive"><a href="../mod/core.html#if">If</a></code> block
are considered, since the first ones are overridden. Using <code class="directive"><a href="#rewriteoptions">RewriteOptions</a></code> Inherit forces mod_rewrite to merge the two
sections and consider both set of statements, rather than only the last one.</li>
</ul>
<div class="example"><pre class="prettyprint lang-config">&lt;If "true"&gt;
 # Without RewriteOptions Inherit, this rule is overridden by the next
 # section and no redirect will happen for URIs containing 'foo'
 RewriteRule foo http://example.com/foo [R]
&lt;/If&gt;
&lt;If "true"&gt;
 RewriteRule bar http://example.com/bar [R]
&lt;/If&gt;</pre>
</div>
</div>

For some hints on <a class="glossarylink" href="../glossary.html#regex" title="see glossary">regular
 expressions</a>, see
 the <a href="../rewrite/intro.html#regex">mod_rewrite
 Introduction</a>.

For information on <a class="glossarylink" href="../glossary.html#regex" title="see glossary">regular
 expressions</a>, including the use of the
 <code>!</code> prefix to negate a pattern, see the
 <a href="../rewrite/intro.html#regex">Regular Expressions</a>
 section of the mod_rewrite introduction.

The <a id="rhs" name="rhs">Substitution</a> of a
 rewrite rule is the string that replaces the original URL-path that
 was matched by Pattern. The Substitution may
 be a:

<dl>

<dt>file-system path</dt>

<dd>Designates the location on the file-system of the resource
 to be delivered to the client. A substitution beginning with
 <code>/</code> is treated as a file-system path only in
 server or virtual host context, and only when the first
 component of the path exists in the file-system. In
 <a class="glossarylink" href="../glossary.html#perdirectory" title="see glossary">per-directory context</a>,
 this guessing does not occur.</dd>

<dd>A <code class="directive"><a href="../mod/core.html#documentroot">DocumentRoot</a></code>-relative path to the
 resource to be served. In server or virtual host context,
 if the first segment of the path exists at the root of the
 file-system, the substitution is treated as a file-system
 path instead. For example, <code>/www/file.html</code> is
 a URL-path unless a directory named <code>www</code> exists
 at the root of the file-system. If you wish other
 URL-mapping directives (such as <code class="directive"><a href="../mod/mod_alias.html#alias">Alias</a></code>) to be applied to the
 resulting URL-path, use the <code>[PT]</code> flag as
 described below.</dd>

<dt>Absolute URL</dt>

<dd>If an absolute URL is specified,
 <code class="module"><a href="../mod/mod_rewrite.html">mod_rewrite</a></code> checks to see whether the
 hostname matches the current host. If it does, the scheme and
 hostname are stripped out and the resulting path is treated as
 a URL-path. Otherwise, an external redirect is performed for
 the given URL. To force an external redirect back to the
 current host, see the <code>[R]</code> flag below.
 Note that a redirect (implicit or not) using an absolute URI
 will include the requested query-string, to prevent this see the
 <code>[QSD]</code> flag below.</dd>

<dd>A dash indicates that no substitution should be performed
 (the existing path is passed through untouched). This is used
 when a flag (see below) needs to be applied without changing
 the path.</dd>

</dl>

<div class="note"><h3>How path substitutions are interpreted</h3>
 Whether a path substitution is treated as a file-system path
 or a URL-path depends on the context and whether it begins with
 a slash:
 <ul>
 <li>Starts with <code>/</code>, server/vhost context:
 Treated as a file-system path if the first path component exists
 on disk; otherwise treated as a URL-path.</li>
 <li>Starts with <code>/</code>, <a class="glossarylink" href="../glossary.html#perdirectory" title="see glossary">per-directory</a> context:
 Always treated as a URL-path. No file-system guessing occurs.</li>
 <li>Does not start with <code>/</code> (relative),
 server/vhost context: Treated as a URL-path relative
 to the current request URI.</li>
 <li>Does not start with <code>/</code> (relative),
 <a class="glossarylink" href="../glossary.html#perdirectory" title="see glossary">per-directory</a> context: Treated as a URL-path relative
 to the directory-path for which the <code class="directive"><a href="../mod/core.html#directory">Directory</a></code> or <code>.htaccess</code>
 applies. See <code class="directive">RewriteBase</code> for controlling
 the prefix added to relative substitutions.</li>
 </ul>
 </div>

In addition to plain text, the Substitution string 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). <code>$0</code> refers to the
 entire string matched by the Pattern, while
 <code>$1</code>..<code>$9</code> refer to the corresponding
 captured groups from the matched Pattern.
 Similarly, back-references
 <code>%0</code>..<code>%9</code> refer to the most recently
 matched
 <code class="directive"><a href="#rewritecond">RewriteCond</a></code>
 CondPattern: <code>%0</code> is the entire match and
 <code>%1</code>..<code>%9</code> are the captured groups. The server variables are the same
 as for the TestString of a
 <code class="directive"><a href="#rewritecond">RewriteCond</a></code>
 directive. The mapping-functions come from the
 <code class="directive"><a href="#rewritemap">RewriteMap</a></code>
 directive and are explained there.
 These three types of variables are expanded in the order above.

Rewrite rules are applied to the results of previous rewrite
 rules, in the order in which they are defined
 in the config file. The URL-path or file-system path (see <a href="#what_is_matched">"What is matched?"</a>, above) is completely
 replaced by the Substitution and the
 rewriting process continues until all rules have been applied,
 or it is explicitly terminated by an
 <a href="../rewrite/flags.html#flag_l"><code>L</code> flag</a>,
 or other flag which implies immediate termination, such as
 <code>END</code> or
 <code>F</code>.

<div class="note"><h3>Modifying the Query String</h3>
 By default, the query string is passed through unchanged. You
 can, however, create URLs in the substitution string containing
 a query string part. Simply use a question mark inside the
 substitution string to indicate that the following text should
 be re-injected into the query string. When you want to erase an
 existing query string, end the substitution string with just a
 question mark. To combine new and old query strings, use the
 <code>[QSA]</code> flag.
 </div>

Additionally you can set special <a name="rewriteflags" id="rewriteflags">actions</a> to be performed by
 appending <code>[</code>flags<code>]</code>
 as the third argument to the <code class="directive">RewriteRule</code>
 directive. Flags is a comma-separated list, surround by square
 brackets, of any of the flags in the following table. More
 details, and examples, for each flag, are available in the <a href="../rewrite/flags.html">Rewrite Flags document</a>.

<table class="bordered"><tr class="header"><th>Flag and syntax</th>
 <th>Function</th>
 </tr>
<tr>
 <td>B</td>
 <td>Escape non-alphanumeric characters in backreferences before
 applying the transformation. For similar escaping of server variables, see
 the "escape" <a href="#mapfunc">mapping-function</a>.<a href="../rewrite/flags.html#flag_b">details ...</a></td>
 </tr>
<tr class="odd">
 <td>BCTLS</td>
 <td>Like [B], but only escape control characters and spaces.
 <a href="../rewrite/flags.html#flag_bctls">details ...</a></td>
 </tr>
<tr>
 <td>BNE</td>
 <td>Characters of [B] or [BCTLS] which should not be escaped.
 <a href="../rewrite/flags.html#flag_bne">details ...</a></td>
 </tr>
<tr class="odd">
 <td>backrefnoplus|BNP</td>
 <td>If backreferences are being escaped, spaces should be escaped to
 %20 instead of +. Useful when the backreference will be used in the
 path component rather than the query string.<a href="../rewrite/flags.html#flag_bnp">details ...</a></td>
 </tr>
<tr>
 <td>chain|C</td>
 <td>Rule is chained to the following rule. If the rule fails,
 the rule(s) chained to it will be skipped. <a href="../rewrite/flags.html#flag_c">details ...</a></td>
 </tr>
<tr class="odd">
 <td>cookie|CO=NAME:VAL</td>
 <td>Sets a cookie in the client browser. Full syntax is:
 CO=NAME:VAL:domain[:lifetime[:path[:secure[:httponly[samesite]]]]] <a href="../rewrite/flags.html#flag_co">details ...</a>
 </td>
 </tr>
<tr>
 <td>discardpath|DPI</td>
 <td>Causes the PATH_INFO portion of the rewritten URI to be
 discarded. <a href="../rewrite/flags.html#flag_dpi">details
 ...</a></td>
 </tr>
<tr class="odd">
 <td>END</td>
 <td>Stop the rewriting process immediately and don't apply any
 more rules. Also prevents further execution of rewrite rules
 in <a class="glossarylink" href="../glossary.html#perdirectory" title="see glossary">per-directory</a> context. (Available in 2.3.9 and later)
 <a href="../rewrite/flags.html#flag_end">details ...</a></td>
 </tr>
<tr>
 <td>env|E=[!]VAR[:VAL]</td>
 <td>Causes an environment variable VAR to be set (to the
 value VAL if provided). The form !VAR causes
 the environment variable VAR to be unset.
 <a href="../rewrite/flags.html#flag_e">details ...</a></td>
 </tr>
<tr class="odd">
 <td>forbidden|F</td>
 <td>Returns a 403 FORBIDDEN response to the client browser.
 <a href="../rewrite/flags.html#flag_f">details ...</a></td>
 </tr>
<tr>
 <td>gone|G</td>
 <td>Returns a 410 GONE response to the client browser. <a href="../rewrite/flags.html#flag_g">details ...</a></td>
 </tr>
<tr class="odd">
 <td>Handler|H=Content-handler</td>
 <td>Causes the resulting URI to be sent to the specified
 Content-handler for processing. <a href="../rewrite/flags.html#flag_h">details ...</a></td>
 </tr>
<tr>
 <td>last|L</td>
 <td>Stop the rewriting process immediately and don't apply any
 more rules. Especially note caveats for <a class="glossarylink" href="../glossary.html#perdirectory" title="see glossary">per-directory</a> context (see also the END flag). <a href="../rewrite/flags.html#flag_l">details ...</a></td>
 </tr>
<tr class="odd">
 <td>next|N</td>
 <td>Re-run the rewriting process, starting again with the first
 rule, using the result of the ruleset so far as a starting
 point. <a href="../rewrite/flags.html#flag_n">details
 ...</a></td>
 </tr>
<tr>
 <td>nocase|NC</td>
 <td>Makes the pattern comparison case-insensitive.
 <a href="../rewrite/flags.html#flag_nc">details ...</a></td>
 </tr>
<tr class="odd">
 <td>noescape|NE</td>
 <td>Prevent mod_rewrite from applying hexcode escaping of
 special characters in the result of rewrites that result in 
 redirection. 
 <a href="../rewrite/flags.html#flag_ne">details ...</a></td>
 </tr>
<tr>
 <td>nosubreq|NS</td>
 <td>Causes a rule to be skipped if the current request is an
 internal sub-request. <a href="../rewrite/flags.html#flag_ns">details ...</a></td>
 </tr>
<tr class="odd">
 <td>proxy|P</td>
 <td>Force the substitution URL to be internally sent as a proxy
 request. <a href="../rewrite/flags.html#flag_p">details
 ...</a></td>
 </tr>
<tr>
 <td>passthrough|PT</td>
 <td>Forces the resulting URI to be passed back to the URL
 mapping engine for processing of other URI-to-filename
 translators, such as <code>Alias</code> or
 <code>Redirect</code>. <a href="../rewrite/flags.html#flag_pt">details ...</a></td>
 </tr>
<tr class="odd">
 <td>qsappend|QSA</td>
 <td>Appends any query string from the original request URL to
 any query string created in the rewrite target.<a href="../rewrite/flags.html#flag_qsa">details ...</a></td>
 </tr>
<tr>
 <td>qsdiscard|QSD</td>
 <td>Discard any query string attached to the incoming URI.
 <a href="../rewrite/flags.html#flag_qsd">details
 ...</a></td>
 </tr>
<tr class="odd">
 <td>qslast|QSL</td>
 <td>Interpret the last (right-most) question mark as the query string
 delimiter, instead of the first (left-most) as normally used. 
 Available in 2.4.19 and later.
 <a href="../rewrite/flags.html#flag_qsl">details
 ...</a></td>
 </tr>
<tr>
 <td>redirect|R[=code]</td>
 <td>Forces an external redirect, optionally with the specified
 HTTP status code. <a href="../rewrite/flags.html#flag_r">details ...</a>
 </td>
 </tr>
<tr class="odd">
 <td>skip|S=num</td>
 <td>Tells the rewriting engine to skip the next num
 rules if the current rule matches. <a href="../rewrite/flags.html#flag_s">details ...</a></td>
 </tr>
<tr>
 <td>type|T=MIME-type</td>
 <td>Force the <a class="glossarylink" href="../glossary.html#mime-type" title="see glossary">MIME-type</a> of the target file
 to be the specified type. <a href="../rewrite/flags.html#flag_t">details ...</a></td>
 </tr>
<tr class="odd">
 <td>UnsafeAllow3F</td>
 <td>Allows substitutions from URL's that may be unsafe.
 <a href="../rewrite/flags.html#flag_unsafe_allow_3f">details ...</a>
 </td>
 </tr>
<tr>
 <td>UnsafePrefixStat</td>
 <td>Allows potentially unsafe substitutions from a leading variable or backreference to a filesystem path.
 <a href="../rewrite/flags.html#flag_unsafe_prefix_stat">details ...</a> 
 Available in Apache HTTP Server 2.4.60 and later.
 </td>
 </tr>
<tr class="odd">
 <td>UNC</td>
 <td>Prevents the merging of multiple leading slashes, as used by Windows UNC paths.
 <a href="../rewrite/flags.html#flag_unc">details ...</a> 
 Available in Apache HTTP Server 2.4.62 and later.
 </td>
 </tr>
</table>

<div class="note"><h3>Home directory expansion</h3>
 When the substitution string begins with a string
resembling "/~user" (via explicit text or backreferences), <code class="module"><a href="../mod/mod_rewrite.html">mod_rewrite</a></code> performs
home directory expansion independent of the presence or configuration
of <code class="module"><a href="../mod/mod_userdir.html">mod_userdir</a></code>.

This expansion does not occur when the PT
flag is used on the <code class="directive">RewriteRule</code>
directive.
</div>

Here are the possible combinations of substitution string
 form, context, and the [R] and [P] flags, and their
 meanings:

Outside <a class="glossarylink" href="../glossary.html#perdirectory" title="see glossary">per-directory</a> configuration 
 for request ``<code>GET
 /somepath/pathinfo</code>'':

<table class="bordered"><tr class="header">
<th>Given Rule</th>
<th>Resulting Substitution</th>
</tr>
<tr>
<td>^/somepath(.*) otherpath$1</td>
<td>invalid, not supported</td>
</tr>
<tr class="odd">
<td>^/somepath(.*) otherpath$1 [R]</td>
<td>invalid, not supported</td>
</tr>
<tr>
<td>^/somepath(.*) otherpath$1 [P]</td>
<td>invalid, not supported</td>
</tr>
<tr class="odd">
<td>^/somepath(.*) /otherpath$1</td>
<td>/otherpath/pathinfo</td>
</tr>
<tr>
<td>^/somepath(.*) /otherpath$1 [R]</td>
<td>http://thishost/otherpath/pathinfo via external redirection</td>
</tr>
<tr class="odd">
<td>^/somepath(.*) /otherpath$1 [P]</td>
<td>doesn't make sense, not supported</td>
</tr>
<tr>
<td>^/somepath(.*) http://thishost/otherpath$1</td>
<td>/otherpath/pathinfo</td>
</tr>
<tr class="odd">
<td>^/somepath(.*) http://thishost/otherpath$1 [R]</td>
<td>http://thishost/otherpath/pathinfo via external redirection</td>
</tr>
<tr>
<td>^/somepath(.*) http://thishost/otherpath$1 [P]</td>
<td>doesn't make sense, not supported</td>
</tr>
<tr class="odd">
<td>^/somepath(.*) http://otherhost/otherpath$1</td>
<td>http://otherhost/otherpath/pathinfo via external redirection</td>
</tr>
<tr>
<td>^/somepath(.*) http://otherhost/otherpath$1 [R]</td>
<td>http://otherhost/otherpath/pathinfo via external redirection (the [R] flag is redundant)</td>
</tr>
<tr class="odd">
<td>^/somepath(.*) http://otherhost/otherpath$1 [P]</td>
<td>http://otherhost/otherpath/pathinfo via internal proxy</td>
</tr>
</table>

Inside <a class="glossarylink" href="../glossary.html#perdirectory" title="see glossary">per-directory</a> configuration for
 <code>/somepath</code> 
 (e.g., <code>.htaccess</code> or <code>&lt;Directory&gt;</code>, with
 <code>RewriteBase "/somepath"</code>) 
 for request ``<code>GET
 /somepath/localpath/pathinfo</code>'':

<table class="bordered"><tr class="header">
<th>Given Rule</th>
<th>Resulting Substitution</th>
</tr>
<tr>
<td>^localpath(.*) otherpath$1</td>
<td>/somepath/otherpath/pathinfo</td>
</tr>
<tr class="odd">
<td>^localpath(.*) otherpath$1 [R]</td>
<td>http://thishost/somepath/otherpath/pathinfo via external
redirection</td>
</tr>
<tr>
<td>^localpath(.*) otherpath$1 [P]</td>
<td>doesn't make sense, not supported</td>
</tr>
<tr class="odd">
<td>^localpath(.*) /otherpath$1</td>
<td>/otherpath/pathinfo</td>
</tr>
<tr>
<td>^localpath(.*) /otherpath$1 [R]</td>
<td>http://thishost/otherpath/pathinfo via external redirection</td>
</tr>
<tr class="odd">
<td>^localpath(.*) /otherpath$1 [P]</td>
<td>doesn't make sense, not supported</td>
</tr>
<tr>
<td>^localpath(.*) http://thishost/otherpath$1</td>
<td>/otherpath/pathinfo</td>
</tr>
<tr class="odd">
<td>^localpath(.*) http://thishost/otherpath$1 [R]</td>
<td>http://thishost/otherpath/pathinfo via external redirection</td>
</tr>
<tr>
<td>^localpath(.*) http://thishost/otherpath$1 [P]</td>
<td>doesn't make sense, not supported</td>
</tr>
<tr class="odd">
<td>^localpath(.*) http://otherhost/otherpath$1</td>
<td>http://otherhost/otherpath/pathinfo via external redirection</td>
</tr>
<tr>
<td>^localpath(.*) http://otherhost/otherpath$1 [R]</td>
<td>http://otherhost/otherpath/pathinfo via external redirection (the [R] flag is redundant)</td>
</tr>
<tr class="odd">
<td>^localpath(.*) http://otherhost/otherpath$1 [P]</td>
<td>http://otherhost/otherpath/pathinfo via internal proxy</td>
</tr>
</table>

</div>
</div>
<div class="bottomlang">
Available Languages: <a href="../../en/mod/mod_rewrite.html" title="English">&nbsp;en&nbsp;</a> |
<a href="../../fr/mod/mod_rewrite.html" hreflang="fr" rel="alternate" title="Fran&ccedil;ais">&nbsp;fr&nbsp;</a>
</div><div id="footer">
Copyright 2026 The Apache Software Foundation. Licensed under the <a href="https://www.apache.org/licenses/LICENSE-2.0">Apache License, Version 2.0</a>.
<a href="../mod/index.html">Modules</a> | <a href="../mod/quickreference.html">Directives</a> | <a href="https://cwiki.apache.org/confluence/display/httpd/FAQ">FAQ</a> | <a href="../glossary.html">Glossary</a> | <a href="../sitemap.html">Sitemap</a> | <a href="https://bz.apache.org/bugzilla/enter_bug.cgi?product=Apache%20httpd-2">Report a bug</a></div><script><![CDATA[//><!]]></script>
</body></html>