From: Rich Bowen mod_rewrite to control access to
various resources, and other related techniques.
-This includes many examples of common uses of mod_rewrite,
+This includes many examples of common uses of mod_rewrite,
including detailed descriptions of how each works.
If all you wish to do is deny access to the resource, rather than redirecting that request elsewhere, this can be - accomplished without the use of mod_rewrite:
+ accomplished without the use ofmod_rewrite:
SetEnvIf Referer example\.com localreferer <FilesMatch "\.(jpg|png|gif)$"> @@ -144,7 +144,7 @@ RewriteRule "\.(gif|jpg|png)$" "http://other.example.com/image.gif" [R,NC]
Note that there are methods of accomplishing this which do
- not use mod_rewrite. Note also that any technique that relies on
+ not use mod_rewrite. Note also that any technique that relies on
the clients USER_AGENT string can be circumvented
very easily, since that string can be changed.
- Rather than using mod_rewrite for this, you can accomplish the
+ Rather than using mod_rewrite for this, you can accomplish the
same end using alternate means, as illustrated here:
SetEnvIfNoCase User-Agent ^NameOfBadRobot goaway diff --git a/docs/manual/rewrite/access.html.fr.utf8 b/docs/manual/rewrite/access.html.fr.utf8 index 9787dd8ec3..34af9ad14f 100644 --- a/docs/manual/rewrite/access.html.fr.utf8 +++ b/docs/manual/rewrite/access.html.fr.utf8 @@ -26,6 +26,8 @@
Ce document est un complément à la documentation de référence de
diff --git a/docs/manual/rewrite/access.xml.fr b/docs/manual/rewrite/access.xml.fr
index 9a1dec9620..adefa26176 100644
--- a/docs/manual/rewrite/access.xml.fr
+++ b/docs/manual/rewrite/access.xml.fr
@@ -1,7 +1,7 @@
-
+
diff --git a/docs/manual/rewrite/access.xml.meta b/docs/manual/rewrite/access.xml.meta
index cda0183580..8ffc1d8a49 100644
--- a/docs/manual/rewrite/access.xml.meta
+++ b/docs/manual/rewrite/access.xml.meta
@@ -8,6 +8,6 @@
Although it is possible to handle virtual hosts
-with mod_rewrite, it is seldom the right way. Creating individual
+with mod_rewrite, it is seldom the right way. Creating individual
<VirtualHost> blocks is
almost always the right way to go. In the
event that you have an enormous number of virtual hosts, consider using
diff --git a/docs/manual/rewrite/avoid.html.fr.utf8 b/docs/manual/rewrite/avoid.html.fr.utf8
index 15954368f4..fb244eebaa 100644
--- a/docs/manual/rewrite/avoid.html.fr.utf8
+++ b/docs/manual/rewrite/avoid.html.fr.utf8
@@ -26,6 +26,8 @@
Ce document est un complément à la Documentation de référence de
diff --git a/docs/manual/rewrite/avoid.xml.fr b/docs/manual/rewrite/avoid.xml.fr
index b146a2a8b0..6064035c82 100644
--- a/docs/manual/rewrite/avoid.xml.fr
+++ b/docs/manual/rewrite/avoid.xml.fr
@@ -1,7 +1,7 @@
-
+
diff --git a/docs/manual/rewrite/avoid.xml.meta b/docs/manual/rewrite/avoid.xml.meta
index 9d51904e7b..405691d6af 100644
--- a/docs/manual/rewrite/avoid.xml.meta
+++ b/docs/manual/rewrite/avoid.xml.meta
@@ -8,6 +8,6 @@
The [B] flag instructs RewriteRule to escape non-alphanumeric
characters before applying the transformation.
mod_rewrite has to unescape URLs before mapping them,
+
mod_rewrite has to unescape URLs before mapping them,
so backreferences are unescaped at the time they are applied.
Using the B flag, non-alphanumeric characters in backreferences
will be escaped. For example, consider the rule:
In the example give, the rule doesn't rewrite the request.
-The "-" rewrite target tells mod_rewrite to pass the request
+The "-" rewrite target tells mod_rewrite to pass the request
through unchanged. Instead, it sets a cookie
called 'frontdoor' to a value of 'yes'. The cookie is valid for any host
in the .example.com domain. It is set to expire in 1440
@@ -283,12 +283,12 @@ compares against is the concatenation of the current values of the URI
and PATH_INFO.
The current URI can be the initial URI as requested by the client, the -result of a previous round of mod_rewrite processing, or the result of -a prior rule in the current round of mod_rewrite processing.
+result of a previous round ofmod_rewrite processing, or the result of
+a prior rule in the current round of mod_rewrite processing.
In contrast, the PATH_INFO that is appended to the URI before each
rule reflects only the value of PATH_INFO before this round of
-mod_rewrite processing. As a consequence, if large portions
+mod_rewrite processing. As a consequence, if large portions
of the URI are matched and copied into a substitution in multiple
RewriteRule directives, without regard for
which parts of the URI came from the current PATH_INFO, the final
@@ -297,8 +297,8 @@ URI may have multiple copies of PATH_INFO appended to it.
Use this flag on any substitution where the PATH_INFO that resulted
from the previous mapping of this request to the filesystem is not of
interest. This flag permanently forgets the PATH_INFO established
-before this round of mod_rewrite processing began. PATH_INFO will
-not be recalculated until the current round of mod_rewrite processing
+before this round of mod_rewrite processing began. PATH_INFO will
+not be recalculated until the current round of mod_rewrite processing
completes. Subsequent rules during this round of processing will see
only the direct result of substitutions, without any PATH_INFO
appended.
If used in per-directory context, use only - (dash)
-as the substitution for the entire round of mod_rewrite processing,
+as the substitution for the entire round of mod_rewrite processing,
otherwise the MIME-type set with this flag is lost due to an internal
-re-processing (including subsequent rounds of mod_rewrite processing).
+re-processing (including subsequent rounds of mod_rewrite processing).
The L flag can be useful in this context to end the
-current round of mod_rewrite processing.
mod_rewrite processing.
Since mod_rewrite is so powerful, it can indeed be rather +
Since mod_rewrite is so powerful, it can indeed be rather
complex. This document supplements the reference documentation, and
attempts to allay some of that complexity, and provide highly
annotated examples of common scenarios that you may handle with
- mod_rewrite. But we also attempt to show you when you should not
- use mod_rewrite, and use other standard Apache features instead,
+ mod_rewrite. But we also attempt to show you when you should not
+ use mod_rewrite, and use other standard Apache features instead,
thus avoiding this unnecessary complexity.
mod_rewrite permet de modifier les requêtes
diff --git a/docs/manual/rewrite/index.xml.fr b/docs/manual/rewrite/index.xml.fr
index 20e8a59d23..9b3c045bbf 100644
--- a/docs/manual/rewrite/index.xml.fr
+++ b/docs/manual/rewrite/index.xml.fr
@@ -1,7 +1,7 @@
-
+
diff --git a/docs/manual/rewrite/index.xml.meta b/docs/manual/rewrite/index.xml.meta
index 25046eafe9..96567025f0 100644
--- a/docs/manual/rewrite/index.xml.meta
+++ b/docs/manual/rewrite/index.xml.meta
@@ -8,7 +8,7 @@