Apache HTTP Server Version 2.3
Description: | Provides a rule-based rewriting engine to rewrite requested URLs on the fly |
---|---|
Status: | Extension |
Module Identifier: | rewrite_module |
Source File: | mod_rewrite.c |
The mod_rewrite
module uses a rule-based rewriting
engine, based on a regular-expression parser, to rewrite requested URLs on
the fly. By default, mod_rewrite
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.
mod_rewrite
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 URL
based on server variables, environment variables, HTTP headers, or time
stamps.
mod_rewrite
operates on the full URL path, including the
path-info section. A rewrite rule can be invoked in
httpd.conf
or in .htaccess
. The path generated
by a rewrite rule can include a query string, or can lead to internal
sub-processing, external request redirection, or internal proxy
throughput.
Further details, discussion, and examples, are provided in the detailed mod_rewrite documentation.
Description: | Sets the base URL for per-directory rewrites |
---|---|
Syntax: | RewriteBase URL-path |
Default: | None |
Context: | directory, .htaccess |
Override: | FileInfo |
Status: | Extension |
Module: | mod_rewrite |
The RewriteBase
directive explicitly
sets the base URL-path (not filesystem directory path!) for per-directory rewrites.
When you use a RewriteRule
in a .htaccess
file, mod_rewrite
strips off
the local directory prefix before processing, then rewrites the rest of
the URL. When the rewrite is completed, mod_rewrite
automatically adds the local directory prefix back on to the path.
This directive is required for per-directory rewrites whose context
is a directory made available via the Alias
directive.
If your URL path does not exist verbatim on the filesystem,
or isn't directly under your DocumentRoot
,
you must use RewriteBase
in every
.htaccess
file where you want to use RewriteRule
directives.
The example below demonstrates how to map
http://example.com/myapp/index.html to
/home/www/example/newsite.html, in a .htaccess
file. This
assumes that the content available at
http://example.com/ is on disk at /home/www/example/
RewriteEngine On # The URL-path used to get to this context, not the filesystem path RewriteBase /myapp/ RewriteRule ^index\.html$ newsite.html
Description: | Defines a condition under which rewriting will take place |
---|---|
Syntax: | RewriteCond
TestString CondPattern |
Context: | server config, virtual host, directory, .htaccess |
Override: | FileInfo |
Status: | Extension |
Module: | mod_rewrite |
The RewriteCond
directive defines a
rule condition. One or more RewriteCond
can precede a RewriteRule
directive. The following rule is then only used if both
the current state of the URI matches its pattern, and if these conditions are met.
TestString is a string which can contain the following expanded constructs in addition to plain text:
$N
(0 <= N <= 9). $1 to $9 provide access to the grouped
parts (in parentheses) of the pattern, from the
RewriteRule
which is subject to the current
set of RewriteCond
conditions. $0 provides
access to the whole string matched by that pattern.
%N
(0 <= N <= 9). %1 to %9 provide access to the grouped
parts (again, in parentheses) of the pattern, from the last matched
RewriteCond
in the current set
of conditions. %0 provides access to the whole string matched by
that pattern.
${mapname:key|default}
.
See the documentation for
RewriteMap for more details.
%{
NAME_OF_VARIABLE
}
where NAME_OF_VARIABLE can be a string taken
from the following list:
HTTP headers: | connection & request: | |
---|---|---|
HTTP_USER_AGENT HTTP_REFERER HTTP_COOKIE HTTP_FORWARDED HTTP_HOST HTTP_PROXY_CONNECTION HTTP_ACCEPT |
REMOTE_ADDR REMOTE_HOST REMOTE_PORT REMOTE_USER REMOTE_IDENT REQUEST_METHOD SCRIPT_FILENAME PATH_INFO QUERY_STRING AUTH_TYPE |
|
server internals: | date and time: | specials: |
DOCUMENT_ROOT SERVER_ADMIN SERVER_NAME SERVER_ADDR SERVER_PORT SERVER_PROTOCOL SERVER_SOFTWARE |
TIME_YEAR TIME_MON TIME_DAY TIME_HOUR TIME_MIN TIME_SEC TIME_WDAY TIME |
API_VERSION THE_REQUEST REQUEST_URI REQUEST_FILENAME IS_SUBREQ HTTPS |
These variables all
correspond to the similarly named HTTP
MIME-headers, C variables of the Apache HTTP Server or
struct tm
fields of the Unix system.
Most are documented elsewhere in the Manual or in
the CGI specification. Those that are special to
mod_rewrite include those below.
IS_SUBREQ
API_VERSION
THE_REQUEST
GET
/index.html HTTP/1.1
"). This does not
include any additional headers sent by the
browser.REQUEST_URI
REQUEST_FILENAME
REQUEST_FILENAME
is referenced. Otherwise,
such as when used in virtual host context, the same
value as REQUEST_URI
.HTTPS
mod_ssl
is loaded).Other things you should be aware of:
The variables SCRIPT_FILENAME and REQUEST_FILENAME
contain the same value - the value of the
filename
field of the internal
request_rec
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
uri
field of request_rec
).
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 %{LA-U:REQUEST_FILENAME}
to determine
the final value of REQUEST_FILENAME.
%{ENV:variable}
, 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
getenv()
from the Apache httpd server process.%{SSL:variable}
, where variable is the
name of an SSL environment
variable, can be used whether or not
mod_ssl
is loaded, but will always expand to
the empty string if it is not. Example:
%{SSL:SSL_CIPHER_USEKEYSIZE}
may expand to
128
.%{HTTP:header}
, 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: %{HTTP:Proxy-Connection}
is
the value of the HTTP header
``Proxy-Connection:
''.
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 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 'ornext|OR
' flag
so that certain conditions might not be evaluated at all.
%{LA-U:variable}
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
REMOTE_USER
variable from within the
per-server context (httpd.conf
file) you must
use %{LA-U:REMOTE_USER}
- this
variable is set by the authorization phases, which come
after the URL translation phase (during which mod_rewrite
operates).
On the other hand, because mod_rewrite implements
its per-directory context (.htaccess
file) via
the Fixup phase of the API and because the authorization
phases come before this phase, you just can use
%{REMOTE_USER}
in that context.
%{LA-F:variable}
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.CondPattern is the condition pattern, a regular expression which is applied to the current instance of the TestString. TestString is first evaluated, before being matched against CondPattern.
Remember: CondPattern is a perl compatible regular expression with some additions:
!
' character (exclamation mark) to specify a
non-matching pattern.""
(two quotation marks) this
compares TestString to the empty string.[
flags]
as the third argument to the RewriteCond
directive, where flags is a comma-separated list of any of the
following flags:
nocase|NC
'
(no case)ornext|OR
'
(or next condition)RewriteCond %{REMOTE_HOST} ^host1.* [OR] RewriteCond %{REMOTE_HOST} ^host2.* [OR] RewriteCond %{REMOTE_HOST} ^host3.* RewriteRule ...some special stuff for any of these hosts...
novary|NV
'
(no vary)Example:
To rewrite the Homepage of a site according to the
``User-Agent:
'' header of the request, you can
use the following:
RewriteCond %{HTTP_USER_AGENT} ^Mozilla.* RewriteRule ^/$ /homepage.max.html [L] RewriteCond %{HTTP_USER_AGENT} ^Lynx.* RewriteRule ^/$ /homepage.min.html [L] RewriteRule ^/$ /homepage.std.html [L]
Explanation: If you use a browser which identifies itself as 'Mozilla' (including Netscape Navigator, Mozilla etc), then you get the max homepage (which could include frames, or other special features). If you use the Lynx browser (which is terminal-based), then you get the min homepage (which could be a version designed for easy, text-only browsing). If neither of these conditions apply (you use any other browser, or your browser identifies itself as something non-standard), you get the std (standard) homepage.
Description: | Enables or disables runtime rewriting engine |
---|---|
Syntax: | RewriteEngine on|off |
Default: | RewriteEngine off |
Context: | server config, virtual host, directory, .htaccess |
Override: | FileInfo |
Status: | Extension |
Module: | mod_rewrite |
The RewriteEngine
directive enables or
disables the runtime rewriting engine. If it is set to
off
this module does no runtime processing at
all. It does not even update the SCRIPT_URx
environment variables.
Use this directive to disable the module instead of
commenting out all the RewriteRule
directives!
Note that rewrite configurations are not
inherited by virtual hosts. This means that you need to have a
RewriteEngine on
directive for each virtual host
in which you wish to use rewrite rules.
RewriteMap
directives of the type prg
are not started during server initialization if they're defined in a
context that does not have RewriteEngine
set to
on
Description: | Sets the name of the file used for logging rewrite engine processing |
---|---|
Syntax: | RewriteLog file-path |
Context: | server config, virtual host |
Status: | Extension |
Module: | mod_rewrite |
The RewriteLog
directive sets the name
of the file to which the server logs any rewriting actions it
performs. If the name does not begin with a slash
('/
') then it is assumed to be relative to the
Server Root. The directive should occur only once per
server config.
/dev/null
, because
although the rewriting engine does not then output to a
logfile it still creates the logfile output internally.
This will slow down the server with no advantage
to the administrator! To disable logging either
remove or comment out the RewriteLog
directive or use RewriteLogLevel 0
!
RewriteLog "/usr/local/var/apache/logs/rewrite.log"
Description: | Sets the verbosity of the log file used by the rewrite engine |
---|---|
Syntax: | RewriteLogLevel Level |
Default: | RewriteLogLevel 0 |
Context: | server config, virtual host |
Status: | Extension |
Module: | mod_rewrite |
The RewriteLogLevel
directive sets the
verbosity level of the rewriting logfile. The default level 0
means no logging, while 9 or more means that practically all
actions are logged.
To disable the logging of rewriting actions simply set Level to 0. This disables all rewrite action logs.
RewriteLogLevel 3
Description: | Defines a mapping function for key-lookup |
---|---|
Syntax: | RewriteMap MapName MapType:MapSource
|
Context: | server config, virtual host |
Status: | Extension |
Module: | mod_rewrite |
Compatibility: | The choice of different dbm types is available in Apache HTTP Server 2.0.41 and later |
The RewriteMap
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 MapName 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:
${
MapName :
LookupKey }
${
MapName :
LookupKey |
DefaultValue
}
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.
For example, you might define a
RewriteMap
as:
RewriteMap examplemap txt:/path/to/file/map.txt
You would then be able to use this map in a
RewriteRule
as follows:
RewriteRule ^/ex/(.*) ${examplemap:$1}
The following combinations for MapType and MapSource can be used:
txt
, MapSource: Unix filesystem
path to valid regular file
This is the standard rewriting map feature where the MapSource is a plain ASCII file containing either blank lines, comment lines (starting with a '#' character) or pairs like the following - one per line.
MatchingKey SubstValue
## ## map.txt -- rewriting map ## Ralf.S.Engelschall rse # Bastard Operator From Hell Mr.Joe.Average joe # Mr. Average
RewriteMap real-to-user txt:/path/to/file/map.txt
rnd
, MapSource: Unix filesystem
path to valid regular file
This is identical to the Standard Plain Text variant
above but with a special post-processing feature: After
looking up a value it is parsed according to contained
``|
'' characters which have the meaning of
``or''. In other words they indicate a set of
alternatives from which the actual returned value is
chosen randomly. For example, you might use the following map
file and directives to provide a random load balancing between
several back-end server, via a reverse-proxy. Images are sent
to one of the servers in the 'static' pool, while everything
else is sent to one of the 'dynamic' pool.
Example:
## ## map.txt -- rewriting map ## static www1|www2|www3|www4 dynamic www5|www6
RewriteMap servers rnd:/path/to/file/map.txt
RewriteRule ^/(.*\.(png|gif|jpg)) http://${servers:static}/$1
[NC,P,L]
RewriteRule ^/(.*) http://${servers:dynamic}/$1 [P,L]
dbm[=type]
, MapSource: Unix filesystem
path to valid regular file
Here the source is a binary format DBM file containing the same contents as a Plain Text format file, but in a special representation which is optimized for really fast lookups. The type can be sdbm, gdbm, ndbm, or db depending on compile-time settings. If the type is omitted, the compile-time default will be chosen.
To create a dbm file from a source text file, use the httxt2dbm utility.
$ httxt2dbm -i mapfile.txt -o mapfile.map
int
, MapSource: Internal Apache httpd
function
Here, the source is an internal Apache httpd function. Currently you cannot create your own, but the following functions already exist:
prg
, MapSource: Unix filesystem
path to valid regular file
Here the source is a program, not a map file. To
create it you can use a language of your choice, but
the result has to be an executable program (either
object-code or a script with the magic cookie trick
'#!/path/to/interpreter
' as the first
line).
This program is started once, when the Apache httpd server
is started, and then communicates with the rewriting engine
via its stdin
and stdout
file-handles. For each map-function lookup it will
receive the key to lookup as a newline-terminated string
on stdin
. It then has to give back the
looked-up value as a newline-terminated string on
stdout
or the four-character string
``NULL
'' if it fails (i.e., there
is no corresponding value for the given key).
This feature utilizes the rewrite-map
mutex,
which is required for reliable communication with the program.
The mutex mechanism and lock file can be configured with the
Mutex
directive.
External rewriting programs are not started if they're defined in a
context that does not have RewriteEngine
set to
on
A trivial program which will implement a 1:1 map (i.e., key == value) could be:
#!/usr/bin/perl $| = 1; while (<STDIN>) { # ...put here any transformations or lookups... print $_; }
But be very careful:
stdout
. Avoid this, as it will cause a deadloop!
``$|=1
'' is used above, to prevent this.SQL Query
MapType: dbd
or fastdbd
,
MapSource: An SQL SELECT statement that takes a single
argument and returns a single value.
This uses mod_dbd
to implement a rewritemap
by lookup in an SQL database. There are two forms:
fastdbd
caches database lookups internally,
dbd
doesn't. So dbd
incurs a
performance penalty but responds immediately if the database
contents are updated, while fastdbd
is more
efficient but won't re-read database contents until server
restart.
If a query returns more than one row, a random row from the result set is used.
RewriteMap myquery "fastdbd:SELECT destination FROM rewrite WHERE source = %s"
The RewriteMap
directive can occur more than
once. For each mapping-function use one
RewriteMap
directive to declare its rewriting
mapfile. While you cannot declare a map in
per-directory context it is of course possible to
use this map in per-directory context.
mtime
of the
mapfile changes or the server does a restart. This way you can have
map-functions in rules which are used for every
request. This is no problem, because the external lookup only happens
once!
Description: | Sets some special options for the rewrite engine |
---|---|
Syntax: | RewriteOptions Options |
Context: | server config, virtual host, directory, .htaccess |
Override: | FileInfo |
Status: | Extension |
Module: | mod_rewrite |
Compatibility: | MaxRedirects is no longer available in version 2.1 and
later |
The RewriteOptions
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:
inherit
.htaccess
configuration or
<Directory>
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.Description: | Defines rules for the rewriting engine |
---|---|
Syntax: | RewriteRule
Pattern Substitution [flags] |
Context: | server config, virtual host, directory, .htaccess |
Override: | FileInfo |
Status: | Extension |
Module: | mod_rewrite |
The RewriteRule
directive is the real
rewriting workhorse. The directive can occur more than once,
with each instance defining a single rewrite rule. The
order in which these rules are defined is important - this is the order
in which they will be applied at run-time.
Pattern is a perl compatible regular expression. On the first RewriteRule it is applied to the (%-encoded) URL-path of the request; subsequent patterns are applied to the output of the last matched RewriteRule.
The Pattern will initially be matched against the part of the URL after the hostname and port, and before the query string.
When the RewriteRule appears in per-directory (htaccess) context, the
Pattern is matched against what remains of the URL after removing
the prefix that lead Apache httpd to the current rules (see the
RewriteBase
). The removed prefix
always ends with a slash, meaning the matching occurs against a string which
never has a leading slash. A Pattern with ^/
never
matches in per-directory context.
If you wish to match against the hostname, port, or query string, use a
RewriteCond
with the
%{HTTP_HOST}
, %{SERVER_PORT}
, or
%{QUERY_STRING}
variables respectively. If you wish to
match against the full URL-path in a per-directory (htaccess) RewriteRule,
use the %{REQUEST_URI}
variable.
For some hints on regular expressions, see the mod_rewrite Introduction.
In mod_rewrite, the NOT character
('!
') is also available as a possible pattern
prefix. This enables you to negate a pattern; to say, for instance:
``if the current URL does NOT match this
pattern''. This can be used for exceptional cases, where
it is easier to match the negative pattern, or as a last
default rule.
$N
in the substitution string!
The Substitution of a rewrite rule is the string that replaces the original URL-path that was matched by Pattern. The Substitution may be a:
DocumentRoot
-relative path to the
resource to be served. Note that mod_rewrite
tries to guess whether you have specified a file-system path
or a URL-path by checking to see if the first segment of the
path exists at the root of the file-system. For example, if
you specify a Substitution string of
/www/file.html
, then this will be treated as a
URL-path unless a directory named www
exists at the root or your file-system, in which case it will
be treated as a file-system path. If you wish other
URL-mapping directives (such as Alias
) to be applied to the
resulting URL-path, use the [PT]
flag as
described below.mod_rewrite
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 [R]
flag below.-
(dash)In addition to plain text, the Substition string can include
$N
) to the RewriteRule
pattern%N
) to the last matched
RewriteCond pattern%{VARNAME}
)${mapname:key|default}
)Back-references are identifiers of the form
$
N
(N=0..9), which will be replaced
by the contents of the Nth group of the
matched Pattern. The server-variables are the same
as for the TestString of a RewriteCond
directive. The mapping-functions come from the
RewriteMap
directive and are explained there.
These three types of variables are expanded in the order above.
As already mentioned, all rewrite rules are
applied to the Substitution (in the order in which
they are defined
in the config file). The URL is completely
replaced by the Substitution and the
rewriting process continues until all rules have been applied,
or it is explicitly terminated by a
L
flag.
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
[QSA]
flag.
Additionally you can set special actions to be performed by
appending [
flags]
as the third argument to the RewriteRule
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 Rewrite Flags document.
Flag and syntax | Function |
---|---|
B | Escape non-alphanumeric characters before applying the transformation. details ... |
chain|C | Rule is chained to the following rule. If the rule fails, the rule(s) chained to it will be skipped. details ... |
cookie|CO=NAME:VAL | Sets a cookie in the client browser. Full syntax is: CO=NAME:VAL[:domain[:lifetime[:path[:secure[:httponly]]]]] details ... |
discardpathinfo|DPI | Causes the PATH_INFO portion of the rewritten URI to be discarded. details ... |
env|E=VAR:VAL | Causes an environment variable VAR to be set to the value VAL. details ... |
forbidden|F | Returns a 403 FORBIDDEN response to the client browser. details ... |
gone|G | Returns a 410 GONE response to the client browser. details ... |
Handler|H=Content-handler | Causes the resulting URI to be sent to the specified Content-handler for processing. details ... |
last|L | Stop the rewriting process immediately and don't apply any more rules. Especially note caveats for per-directory and .htaccess context. details ... |
next|N | Re-run the rewriting process, starting again with the first rule, using the result of the ruleset so far as a starting point. details ... |
nocase|NC | Makes the pattern pattern comparison case-insensitive. details ... |
noescape|NE | Prevent mod_rewrite from applying hexcode escaping of special characters in the result of the rewrite. details ... |
nosubreq|NS | Causes a rule to be skipped if the current request is an internal sub-request. details ... |
proxy|P | Force the substitution URL to be internally sent as a proxy request. details ... |
passthrough|PT | Forces the resulting URI to be passed back to the URL
mapping engine for processing of other URI-to-filename
translators, such as Alias or
Redirect . details ... |
qsappend|QSA | Appends any query string created in the rewrite target to any query string that was in the original request URL. details ... |
qsdiscard|QSD | Discard any query string attached to the incoming URI. details ... |
redirect|R[=code] | Forces an external redirect, optionally with the specified HTTP status code. details ... |
skip|S=num | Tells the rewriting engine to skip the next num rules if the current rule matches. details ... |
tyle|T=MIME-type | Force the MIME-type of the target file to be the specified type. details ... |
When the substitution string begins with a string
resembling "/~user" (via explicit text or backreferences), mod_rewrite performs
home directory expansion independent of the presence or configuration
of mod_userdir
.
This expansion does not occur when the PT
flag is used on the RewriteRule
directive.
The rewrite engine may be used in .htaccess files. To enable the
rewrite engine for these files you need to set
"RewriteEngine On
" and
"Options FollowSymLinks
" must be enabled. If your
administrator has disabled override of FollowSymLinks
for
a user's directory, then you cannot use the rewrite engine. This
restriction is required for security reasons.
When using the rewrite engine in .htaccess
files the
per-directory prefix (which always is the same for a specific
directory) is automatically removed for the pattern matching
and automatically added after the substitution has been
done. This feature is essential for many sorts of rewriting; without
this, you would always have to match the parent directory, which is
not always possible. There is one exception: If a substitution string
starts with http://
, then the directory prefix will
not be added, and an external redirect (or proxy
throughput, if using flag P) is forced. See the
RewriteBase
directive for
more information.
The rewrite engine may also be used in <Directory>
sections with the same
prefix-matching rules as would be applied to .htaccess
files. It is usually simpler, however, to avoid the prefix substitution
complication by putting the rewrite rules in the main server or
virtual host context, rather than in a <Directory>
section.
Although rewrite rules are syntactically permitted in <Location>
and <Files>
sections, this
should never be necessary and is unsupported.
Here are all possible substitution combinations and their meanings:
Inside per-server configuration
(httpd.conf
)
for request ``GET
/somepath/pathinfo
'':
Given Rule Resulting Substitution ---------------------------------------------- ---------------------------------- ^/somepath(.*) otherpath$1 invalid, not supported ^/somepath(.*) otherpath$1 [R] invalid, not supported ^/somepath(.*) otherpath$1 [P] invalid, not supported ---------------------------------------------- ---------------------------------- ^/somepath(.*) /otherpath$1 /otherpath/pathinfo ^/somepath(.*) /otherpath$1 [R] http://thishost/otherpath/pathinfo via external redirection ^/somepath(.*) /otherpath$1 [P] doesn't make sense, not supported ---------------------------------------------- ---------------------------------- ^/somepath(.*) http://thishost/otherpath$1 /otherpath/pathinfo ^/somepath(.*) http://thishost/otherpath$1 [R] http://thishost/otherpath/pathinfo via external redirection ^/somepath(.*) http://thishost/otherpath$1 [P] doesn't make sense, not supported ---------------------------------------------- ---------------------------------- ^/somepath(.*) http://otherhost/otherpath$1 http://otherhost/otherpath/pathinfo via external redirection ^/somepath(.*) http://otherhost/otherpath$1 [R] http://otherhost/otherpath/pathinfo via external redirection (the [R] flag is redundant) ^/somepath(.*) http://otherhost/otherpath$1 [P] http://otherhost/otherpath/pathinfo via internal proxy
Inside per-directory configuration for
/somepath
(/physical/path/to/somepath/.htacccess
, with
RewriteBase /somepath
)
for request ``GET
/somepath/localpath/pathinfo
'':
Given Rule Resulting Substitution ---------------------------------------------- ---------------------------------- ^localpath(.*) otherpath$1 /somepath/otherpath/pathinfo ^localpath(.*) otherpath$1 [R] http://thishost/somepath/otherpath/pathinfo via external redirection ^localpath(.*) otherpath$1 [P] doesn't make sense, not supported ---------------------------------------------- ---------------------------------- ^localpath(.*) /otherpath$1 /otherpath/pathinfo ^localpath(.*) /otherpath$1 [R] http://thishost/otherpath/pathinfo via external redirection ^localpath(.*) /otherpath$1 [P] doesn't make sense, not supported ---------------------------------------------- ---------------------------------- ^localpath(.*) http://thishost/otherpath$1 /otherpath/pathinfo ^localpath(.*) http://thishost/otherpath$1 [R] http://thishost/otherpath/pathinfo via external redirection ^localpath(.*) http://thishost/otherpath$1 [P] doesn't make sense, not supported ---------------------------------------------- ---------------------------------- ^localpath(.*) http://otherhost/otherpath$1 http://otherhost/otherpath/pathinfo via external redirection ^localpath(.*) http://otherhost/otherpath$1 [R] http://otherhost/otherpath/pathinfo via external redirection (the [R] flag is redundant) ^localpath(.*) http://otherhost/otherpath$1 [P] http://otherhost/otherpath/pathinfo via internal proxy