From cvs-return-44020-apmail-httpd-cvs-archive=httpd.apache.org@httpd.apache.org Wed Jul 18 13:16:52 2012
Return-Path:
Using the [END] flag terminates not only the current round of rewrite processing (like [L]) but also prevents any subsequent rewrite processing from occurring in per-directory (htaccess) context.
@@ -505,6 +505,15 @@ and hostname part of the URL is either f client undue influence.Using this flag triggers the use of mod_proxy, without handling of persistent connections. This
+means the performance of your proxy will be better if you set it up with ProxyPass or
+ProxyPassMatch
This is because this flag triggers the use of the default worker, which does not handle connection pooling.
+Avoid using this flag and prefer those directives, whenever you can.
+Note: mod_proxy must be enabled in order
to use this flag.
L were used.
@@ -629,11 +638,11 @@ URI in request' warnings.
The [S] flag is used to skip rules that you don't want to run. The
-syntax of the skip flag is [S=N], where N signifies
-the number of rules to skip. This can be thought of as a goto
-statement in your rewrite ruleset. In the following example, we only want
-to run the RewriteRule if the
+
The [S] flag is used to skip rules that you don't want to run. The
+syntax of the skip flag is [S=N], where N signifies
+the number of rules to skip. This can be thought of as a goto
+statement in your rewrite ruleset. In the following example, we only want
+to run the RewriteRule if the
requested URI doesn't correspond with an actual file.
Modified: httpd/httpd/branches/2.4.x/docs/manual/rewrite/flags.xml URL: http://svn.apache.org/viewvc/httpd/httpd/branches/2.4.x/docs/manual/rewrite/flags.xml?rev=1362933&r1=1362932&r2=1362933&view=diff ============================================================================== --- httpd/httpd/branches/2.4.x/docs/manual/rewrite/flags.xml (original) +++ httpd/httpd/branches/2.4.x/docs/manual/rewrite/flags.xml Wed Jul 18 13:16:24 2012 @@ -261,7 +261,7 @@ module="mod_setenvif">SetEnvIf -END +END Using the [END] flag terminates not only the current round of rewrite processing (like [L]) but also prevents any subsequent rewrite processing from occurring in per-directory (htaccess) context.
@@ -489,6 +489,15 @@ and hostname part of the URL is either f client undue influence. ++ +Performance warning +Using this flag triggers the use of
+mod_proxy , without handling of persistent connections. This +means the performance of your proxy will be better if you set it up withProxyPass or +ProxyPassMatch This is because this flag triggers the use of the default worker, which does not handle connection pooling.
+Avoid using this flag and prefer those directives, whenever you can.
+Note:
@@ -597,7 +606,7 @@ will be used to generate the URL sent wi Any valid HTTP response status code may be specified, using the syntax [R=305], with a 302 status code being used by default if none is specified. The status code specified need not -necessarily be a redirect (3xx) status code. However, +necessarily be a redirect (3xx) status code. However, if a status code is outside the redirect range (300-399) then the substitution string is dropped entirely, and rewriting is stopped as if themod_proxy must be enabled in order to use this flag.Lwere used. @@ -617,11 +626,11 @@ URI in request' warnings.S|skip -The [S] flag is used to skip rules that you don't want to run. The -syntax of the skip flag is [S=N], where N signifies -the number of rules to skip. This can be thought of as a
goto-statement in your rewrite ruleset. In the following example, we only want -to run theRewriteRule if the +The [S] flag is used to skip rules that you don't want to run. The +syntax of the skip flag is [S=N], where N signifies +the number of rules to skip. This can be thought of as a
goto+statement in your rewrite ruleset. In the following example, we only want +to run theRewriteRule if the requested URI doesn't correspond with an actual file.