From: Christophe Jaillet RewriteEngine on
RewriteBase "/~quux/"
-RewriteRule "^foo\.html$" "foo.cgi" [H=cgi-script]
+RewriteRule "^foo\.html$" "foo.cgi" [H=cgi-script]
@@ -294,7 +294,7 @@ hostname(s).
<If "%{HTTP_HOST} != 'www.example.com'"> - Redirect "/" "http://www.example.com/" + Redirect "/" "http://www.example.com/" </If>@@ -302,7 +302,7 @@ directive: might do the following:
<If "%{SERVER_PROTOCOL} != 'HTTPS'"> - Redirect "/admin/" "https://www.example.com/admin/" + Redirect "/admin/" "https://www.example.com/admin/" </If>@@ -314,7 +314,7 @@ you might use one of the recipes below.
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]+RewriteRule "^/?(.*)" "http://www.example.com:%{SERVER_PORT}/$1" [L,R,NE]
And for a site running on port 80
@@ -625,7 +625,7 @@ of the URL.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 +condition is a bit complex for flexibility and to avoid double '&&' in the substitutions.
# The desired URL might be /products/kitchen-sink, and the script expects +# The desired URL might be /products/kitchen-sink, and the script expects # /path?products=kitchen-sink. RewriteRule "^/?path/([^/]+)/([^/]+)" "/path?$1=$2" [PT]diff --git a/docs/manual/rewrite/remapping.xml.fr b/docs/manual/rewrite/remapping.xml.fr index 68723e92f1b..6b63c875d6c 100644 --- a/docs/manual/rewrite/remapping.xml.fr +++ b/docs/manual/rewrite/remapping.xml.fr @@ -1,7 +1,7 @@ - + diff --git a/docs/manual/rewrite/remapping.xml.meta b/docs/manual/rewrite/remapping.xml.meta index fc4dfefebf2..5e5f6e1602e 100644 --- a/docs/manual/rewrite/remapping.xml.meta +++ b/docs/manual/rewrite/remapping.xml.meta @@ -8,6 +8,6 @@en -fr +fr