http://httpd.apache.org/docs/2.4/en/rewrite/remapping.html
使用mod_rewrite重定向和重映射（Redirecting and Remapping with mod_rewrite）
This document supplements the mod_rewrite reference documentation. It describes how you can use mod_rewrite to redirect and remap request. This includes many examples of common uses of mod_rewrite, including detailed descriptions of how each works.
本文件是mod_rewrite 对参考文件的补充。它描述了如何使用mod_rewrite重定向和重新映射请求。这包括mod_rewrite常用用法的很多例子，包括每个工作原理的详细描述。
Note that many of these examples won’t work unchanged in your particular server configuration, so it’s important that you understand them, rather than merely cutting and pasting the examples into your configuration.
请注意，这些示例中的很多不会在特定的服务器配置中保持不变，因此重要的是要了解它们，而不是仅将示例剪切并粘贴到配置中。
从旧到新（内部） From Old to New (internal)
Description:
Assume we have recently renamed the page foo.html to bar.html and now want to provide the old URL for backward compatibility. However, we want that users of the old URL even not recognize that the pages was renamed - that is, we don’t want the address to change in their browser.
假设我们最近将 foo.htm重命名为bar.html，并且现在想要提供旧的URL以实现向后兼容。但是，我们希望用户不知道网页已重命名 - 也就是说，我们不希望地址在其浏览器中更改。
Solution:
We rewrite the old URL to the new one internally via the following rule:
我们通过以下规则在内部重新编写旧的URL：
RewriteEngine on
RewriteRule "^/foo\.html$" "/bar.html" [PT]重写从旧到新（外部）Rewriting From Old to New (external)
Description:
Assume again that we have recently renamed the page foo.html to bar.html and now want to provide the old URL for backward compatibility. But this time we want that the users of the old URL get hinted to the new one, i.e. their browsers Location field should change, too.
再假设我们最近将 foo.htm重命名为bar.html，并且想要提供旧的URL以实现向后兼容。但是这次我们希望给用户暗示新的网址，即他们的浏览器Location也应该改变。
Solution:
We force a HTTP redirect to the new URL which leads to a change of the browsers and thus the users view:
我们强制HTTP重定向到新的URL，导致浏览器发生更改，因此用户查看：
RewriteEngine on
RewriteRule "^/foo\.html$" "bar.html" [R]Discussion
In this example, as contrasted to the internal example above, we can simply use the Redirect directive. mod_rewrite was used in that earlier example in order to hide the redirect from the client:
在这个例子中，与上面的内部例子相比，我们可以简单地使用Redirect指令。在前面的例子中使用了mod_rewrite来隐藏来自客户端的重定向：
Redirect "/foo.html" "/bar.html"资源移动到另一台服务器（Resource Moved to Another Server）
Description:
If a resource has moved to another server, you may wish to have URLs continue to work for a time on the old server while people update their bookmarks.
如果某个资源已移至其他服务器，您可能希望旧版服务器上的网址继续运行一段时间，同时人们更新其书签。
Solution:
You can use mod_rewrite to redirect these URLs to the new server, but you might also consider using the Redirect or
RedirectMatch directive.
您可以使用mod_rewrite将这些URL重定向到新服务器，但您也可以考虑使用Redirect或RedirectMatch指令。
#With mod_rewrite
RewriteEngine on
RewriteRule "^/docs/(.+)" "http://new.example.com/docs/$1" [R,L]#With RedirectMatch
RedirectMatch "^/docs/(.*)" "http://new.example.com/docs/$1"#With Redirect
Redirect "/docs/" "http://new.example.com/docs/"从静态到动态（From Static to Dynamic）
Description:
How can we transform a static page foo.html into a dynamic variant foo.cgi in a seamless way, i.e. without notice by the browser/user.
我们如何能够以无缝的方式将静态页面 foo.html转换为动态变体 foo.cgi，即无需浏览器/用户注意。
Solution:
We just rewrite the URL to the CGI-script and force the handler to be cgi-script so that it is executed as a CGI program. This way a request to /~quux/foo.html internally leads to the invocation of /~quux/foo.cgi.
我们只需将URL重写为CGI脚本，并强制该处理程序为CGI脚本，以便它作为CGI程序执行。这样一个/~quux/foo.html 内部导致调用的请求/~quux/foo.cgi。
RewriteEngine on
RewriteBase "/~quux/"
RewriteRule "^foo\.html$" "foo.cgi" [H=cgi-script]向后兼容性文件扩展名更改（Backward Compatibility for file extension change）
Description:
How can we make URLs backward compatible (still existing virtually) after migrating document.YYYY to document.XXXX, e.g. after translating a bunch of .html files to .php?
在将document.YYYY移植到document.XXXX后，我们如何使URL向后兼容（虚拟地存在），例如在将一堆.html文件翻译为.php之后？
Solution:
We rewrite the name to its basename and test for existence of the new extension. If it exists, we take that name, else we rewrite the URL to its original state.
我们将该名称重写为其基本名称并测试新扩展的是否存在。如果它存在，我们将采用该名称，否则我们将URL重写为其原始状态。
# backward compatibility ruleset for 向后兼容性规则集
# rewriting document.html to document.php
# when and only when document.php exists
<Directory "/var/www/htdocs">
RewriteEngine on
RewriteBase "/var/www/htdocs"
RewriteCond "$1.php" -f
RewriteCond "$1.html" !-f
RewriteRule "^(.*).html$" "$1.php"
</Directory>Discussion
This example uses an often-overlooked feature of mod_rewrite, by taking advantage of the order of execution of the ruleset. In particular, mod_rewrite evaluates the left-hand-side of the RewriteRule before it evaluates the RewriteCond directives. Consequently, $1 is already defined by the time the RewriteCond directives are evaluated. This allows us to test for the existence of the original (document.html) and target (document.php) files using the same base filename.
通过利用规则集的执行顺序，本示例使用了mod_rewrite的一个经常被忽略的特性。特别是，在评估RewriteCond指令之前，mod_rewrite会评估RewriteRule的左侧。因此，在评估RewriteCond指令时已经定义了$ 1。这使我们可以使用相同的基本文件名来测试原始（document.html）和目标（document.php）文件的存在。
This ruleset is designed to use in a per-directory context (In a <Directory> block or in a .htaccess file), so that the -f checks are looking at the correct directory path. You may need to set a RewriteBase directive to specify the directory base that you’re working in.
此规则集旨在用于每个目录上下文（在<Directory>块或.htaccess文件中），以便 -f 检查查看正确的目录路径。您可能需要设置RewriteBase指令来指定您所在的目录库。
规范主机名称（Canonical Hostnames）
Description:
The goal of this rule is to force the use of a particular hostname, in preference to other hostnames which may be used to reach the same site. For example, if you wish to force the use of www.example.com instead of example.com, you might use a variant of the following recipe.
此规则的目标是强制使用特定的主机名，而不是其他可用于访问同一站点的主机名。例如，如果您希望强制使用www.example.com而不是 example.com，则可以使用以下配方的变体。
Solution:
The very best way to solve this doesn’t involve mod_rewrite at all, but rather uses the Redirect directive placed in a virtual host for the non-canonical hostname(s).
解决这个问题的最好方法根本不涉及mod_rewrite，而是使用Redirect 放置在虚拟主机中的非指定主机名的指令。
<VirtualHost *:80>
ServerName undesired.example.com
ServerAlias example.com notthis.example.com
Redirect "/" "http://www.example.com/"
</VirtualHost>
<VirtualHost *:80>
ServerName www.example.com
</VirtualHost>You can alternatively accomplish this using the <If> directive:
您也可以使用该<If> 指令来完成此操作 ：
<If "%{HTTP_HOST} != 'www.example.com'">
Redirect "/" "http://www.example.com/"
</If>Or, for example, to redirect a portion of your site to HTTPS, you might do the following:
或者，例如，要将网站的一部分重定向到HTTPS，您可以执行以下操作：
<If "%{SERVER_PROTOCOL} != 'HTTPS'">
Redirect "/admin/" "https://www.example.com/admin/"
</If>If, for whatever reason, you still want to use mod_rewrite - if, for example, you need this to work with a larger set of RewriteRules - you might use one of the recipes below.
如果无论出于何种原因，您仍然想使用mod_rewrite - 例如，您需要使用更大的一套RewriteRules - 您可以使用下面的一个配方。
For sites running on a port other than 80:
对于在80以外的端口上运行的站点：
RewriteCond "%{HTTP_HOST}" "!^www\.example\.com" [NC]
RewriteCond "%{HTTP_HOST}" "!^$"
RewriteCond "%{SERVER_PORT}" "!^80$"
RewriteRule "^/?(.*)" "http://www.example.com:%{SERVER_PORT}/$1" [L,R,NE]And for a site running on port 80
对于在80端口上运行的站点
RewriteCond "%{HTTP_HOST}" "!^www\.example\.com" [NC]
RewriteCond "%{HTTP_HOST}" "!^$"
RewriteRule "^/?(.*)" "http://www.example.com/$1" [L,R,NE]If you wanted to do this generically for all domain names - that is, if you want to redirect example.com to www.example.com for all possible values of example.com, you could use the following recipe:
如果您想为所有域名一般做到这一点-那就是，如果你想重定向example.com到 www.example.com的所有可能的值 example.com，你可以使用下面的方法：
RewriteCond "%{HTTP_HOST}" "!^www\." [NC]
RewriteCond "%{HTTP_HOST}" "!^$"
RewriteRule "^/?(.*)" "http://www.%{HTTP_HOST}/$1" [L,R,NE]These rulesets will work either in your main server configuration file, or in a .htaccess file placed in the DocumentRoot of the server.
这些规则集既可以在您的主服务器配置文件中，也可以在.htaccess放置在DocumentRoot服务器中的文件中使用。
在多个目录中搜索页面（Search for pages in more than one directory）
Description:
A particular resource might exist in one of several places, and we want to look in those places for the resource when it is requested. Perhaps we’ve recently rearranged our directory structure, dividing content into several locations.
某个特定资源可能存在于其中一个地方，我们希望在请求时在这些地方查找资源。也许我们最近重新安排了我们的目录结构，将内容分成几个位置。
Solution:
The following ruleset searches in two directories to find the resource, and, if not finding it in either place, will attempt to just serve it out of the location requested.
以下规则集在两个目录中搜索以查找资源，如果在任一位置都找不到，将尝试从请求的位置出来。
RewriteEngine on
# first try to find it in dir1/...
# ...and if found stop and be happy:
RewriteCond "%{DOCUMENT_ROOT}/dir1/%{REQUEST_URI}" -f
RewriteRule "^(.+)" "%{DOCUMENT_ROOT}/dir1/$1" [L]
# second try to find it in dir2/...
# ...and if found stop and be happy:
RewriteCond "%{DOCUMENT_ROOT}/dir2/%{REQUEST_URI}" -f
RewriteRule "^(.+)" "%{DOCUMENT_ROOT}/dir2/$1" [L]
# else go on for other Alias or ScriptAlias directives,
# etc.
RewriteRule "^" "-" [PT]重定向到地理分布式服务器（Redirecting to Geographically Distributed Servers）
Description:
We have numerous mirrors of our website, and want to redirect people to the one that is located in the country where they are located.
我们网站上有许多镜像，并希望将用户重定向到位于所在国家/地区的用户。
Solution:
Looking at the hostname of the requesting client, we determine which country they are coming from. If we can’t do a lookup on their IP address, we fall back to a default server.
查看请求客户的主机名，我们确定他们来自哪个国家。如果我们无法查询他们的IP地址，我们会回到默认服务器。
We’ll use a RewriteMap directive to build a list of servers that we wish to use.
我们将使用RewriteMap 指令来构建我们希望使用的服务器列表。
HostnameLookups on
RewriteEngine on
RewriteMap multiplex "txt:/path/to/map.mirrors"
RewriteCond "%{REMOTE_HOST}" "([a-z]+)$" [NC]
RewriteRule "^/(.*)$" "${multiplex:%1|http://www.example.com/}$1" [R,L]## map.mirrors -- Multiplexing Map
de http://www.example.de/
uk http://www.example.uk/
com http://www.example.com/
##EOF##Discussion
This ruleset relies on HostNameLookups being set on, which can be a significant performance hit.
这个规则集依赖于 HostNameLookups 被设置on，这可能是一个重大的性能影响。
The RewriteCond directive captures the last portion of the hostname of the requesting client - the country code - and the following RewriteRule uses that value to look up the appropriate mirror host in the map file.
该RewriteCond 指令捕获请求客户端的主机名的最后一部分 - 国家代码 - 并且以下RewriteRule使用该值在映射文件中查找适当的镜像主机。
浏览器依赖内容（Browser Dependent Content）
Description:
We wish to provide different content based on the browser, or user-agent, which is requesting the content.
我们希望基于浏览器或用户代理，其请求的内容上，以提供不同的内容。
Solution:
We have to decide, based on the HTTP header “User-Agent”, which content to serve. The following config does the following: If the HTTP header “User-Agent” contains “Mozilla/3”, the page foo.html is rewritten to foo.NS.html and the rewriting stops. If the browser is “Lynx” or “Mozilla” of version 1 or 2, the URL becomes foo.20.html. All other browsers receive page foo.32.html. This is done with the following ruleset:
我们必须根据HTTP头“User-Agent”决定要提供哪些内容。以下配置会执行以下操作：如果HTTP头“User-Agent”包含“Mozilla / 3”，则页面foo.html 被重写foo.NS.html并停止重写。如果浏览器是版本1或2的“Lynx”或“Mozilla”，则URL将变为foo.20.html。所有其他浏览器都会收到页面foo.32.html。这是通过以下规则集完成的：
RewriteCond "%{HTTP_USER_AGENT}" "^Mozilla/3.*"
RewriteRule "^foo\.html$" "foo.NS.html" [L]
RewriteCond "%{HTTP_USER_AGENT}" "^Lynx/" [OR]
RewriteCond "%{HTTP_USER_AGENT}" "^Mozilla/[12]"
RewriteRule "^foo\.html$" "foo.20.html" [L]
RewriteRule "^foo\.html$" "foo.32.html" [L]规范网址（Canonical URLs）
Description:
On some webservers there is more than one URL for a resource. Usually there are canonical URLs (which are be actually used and distributed) and those which are just shortcuts, internal ones, and so on. Independent of which URL the user supplied with the request, they should finally see the canonical one in their browser address bar.
在一些Web服务器上，有多个URL用于资源。通常有规范的URL（实际使用和分发）以及那些只是快捷方式，内部的URL等等。独立于用户提供请求的URL，他们最终应该在浏览器地址栏中看到规范的URL。
Solution:
We do an external HTTP redirect for all non-canonical URLs to fix them in the location view of the Browser and for all subsequent requests. In the example ruleset below we replace /puppies and /canines by the canonical /dogs.
我们对所有非规范URL进行外部HTTP重定向，以将其修复到浏览器的位置视图以及所有后续请求中。在下面的示例规则集中，我们用规范/dogs替换/puppies 和/canines 。
RewriteRule "^/(puppies|canines)/(.*)" "/dogs/$2" [R]Discussion:
This should really be accomplished with Redirect or RedirectMatch directives:
这应该通过重定向或RedirectMatch指令来实现：
RedirectMatch "^/(puppies|canines)/(.*)" "/dogs/$2"移动 DocumentRoot（Moved DocumentRoot）
Description:
Usually the DocumentRoot of the webserver directly relates to the URL “/”. But often this data is not really of top-level priority. For example, you may wish for visitors, on first entering a site, to go to a particular subdirectory /about/. This may be accomplished using the following ruleset:
通常DocumentRoot ，网络服务器直接与URL“ /”相关。但通常这些数据并不是真正的最高优先级。例如，您可能希望访问者在首次进入某个网站时转到特定的子目录/about/。这可以使用以下规则集来完成：
Solution:
We redirect the URL / to /about/:
我们将URL重定向/到 /about/：
RewriteEngine on
RewriteRule "^/$" "/about/" [R]Note that this can also be handled using the RedirectMatch directive:
请注意，这也可以使用RedirectMatch指令处理：
RedirectMatch "^/$" "http://example.com/about/"Note also that the example rewrites only the root URL. That is, it rewrites a request for http://example.com/, but not a request for http://example.com/page.html. If you have in fact changed your document root - that is, if all of your content is in fact in that subdirectory, it is greatly preferable to simply change your DocumentRoot directive, or move all of the content up one directory, rather than rewriting URLs.
另请注意，该示例仅重写根URL。也就是说，它会重写请求http://example.com/，但不会请求http://example.com/page.html。如果你实际上已经改变了你的文档根目录 - 也就是说，如果你的所有内容实际上都在该子目录中，那么简单地改变你的DocumentRoot 指令或者将所有内容移动到一个目录而不是重写URL 是非常可取的。
后备资源（Fallback Resource）
Description:
You want a single resource (say, a certain file, like index.php) to handle all requests that come to a particular directory, except those that should go to an existing resource such as an image, or a css file.
你需要一个资源（比如index.php等特定文件）来处理所有到达某个特定目录的请求，除了那些应该转到现有资源（如图像或css文件）的请求。
Solution:
As of version 2.2.16, you should use the FallbackResource directive for this:
从版本2.2.16开始，您应该使用以下FallbackResource指令：
<Directory "/var/www/my_blog">
FallbackResource "index.php"
</Directory>However, in earlier versions of Apache, or if your needs are more complicated than this, you can use a variation of the following rewrite set to accomplish the same thing:
但是，在较早版本的Apache中，或者如果您的需求比这更复杂，则可以使用以下重写集的变体来完成同样的事情：
<Directory "/var/www/my_blog">
RewriteBase "/my_blog"
RewriteCond "/var/www/my_blog/%{REQUEST_FILENAME}" !-f
RewriteCond "/var/www/my_blog/%{REQUEST_FILENAME}" !-d
RewriteRule "^" "index.php" [PT]
</Directory>on the other hand,If you wish to pass the requested URI as a query string argument to index.php, you can replace that RewriteRule with:
另一方面，如果您希望将请求的URI作为查询字符串参数传递给index.php，则可以将该RewriteRule替换为：
RewriteRule "(.*)" "index.php?$1" [PT,QSA]Note that these rulesets can be used in a .htaccess file, as well as in a <Directory> block.
请注意，这些规则集可以在.htaccess 文件中使用，也可以在<Directory>块中使用。
重写查询字符串（Rewrite query string）
Description:
You want to capture a particular value from a query string and either replace it or incorporate it into another component of the URL.
您希望从查询字符串中捕获特定值，并将其替换或将其合并到URL的另一个组件中。
Solutions:
Many of the solutions in this section will all use the same condition, which leaves the matched value in the %2 backreference. %1 is the beginining of the query string (up to the key of intererest), and %3 is the remainder. This condition is a bit complex for flexibility and to avoid double ‘&&’ in the substitutions.
本节中的许多解决方案都将使用相同的条件，这会在％2反向引用中留下匹配的值。％1是查询字符串的开始（直到intererest的关键字），并且％3是余数。这种情况对于灵活性有点复杂，并且在替换中避免双重’&&’。
- This solution removes the matching key and value:
该解决方案删除了匹配键和值：
# Remove mykey=???
RewriteCond "%{QUERY_STRING}" "(.*(?:^|&))mykey=([^&]*)&?(.*)&?$"
RewriteRule "(.*)" "$1?%1%3"- This solution uses the captured value in the URL subsitution, discarding the rest of the original query by appending a ‘?’:
此解决方案使用URL替换中的捕获值，通过追加’？’来丢弃原始查询的其余部分：
# Copy from query string to PATH_INFO
RewriteCond "%{QUERY_STRING}" "(.*(?:^|&))mykey=([^&]*)&?(.*)&?$"
RewriteRule "(.*)" "$1/products/%2/?" [PT]- This solution checks the captured value in a subsequent condition:
该解决方案在后续条件中检查捕获的值：
# Capture the value of mykey in the query string
RewriteCond "%{QUERY_STRING}" "(.*(?:^|&))mykey=([^&]*)&?(.*)&?$"
RewriteCond "%2" !=not-so-secret-value
RewriteRule "(.*)" - [F]- This solution shows the reverse of the previous ones, copying path components (perhaps PATH_INFO) from the URL into the query string.
此解决方案显示了与之前相反的方法，将URL中的路径组件（可能是PATH_INFO）复制到查询字符串中。
# The desired URL might be /products/kitchen-sink, and the script expects
# /path?products=kitchen-sink.
RewriteRule "^/?path/([^/]+)/([^/]+)" "/path?$1=$2" [PT]