From a4cb87abaf4d7e92215c690e487692fa612f6abc Mon Sep 17 00:00:00 2001 From: Eric Covener Date: Thu, 19 May 2022 18:43:39 +0000 Subject: [PATCH] escaping doesn't actually happen by default otherwise, we would not have [B] and two internal escape functions. git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/trunk@1901071 13f79535-47bb-0310-9956-ffa450edef68 --- docs/manual/mod/mod_rewrite.xml | 5 +++-- docs/manual/rewrite/flags.xml | 3 ++- 2 files changed, 5 insertions(+), 3 deletions(-) diff --git a/docs/manual/mod/mod_rewrite.xml b/docs/manual/mod/mod_rewrite.xml index 961c7c313fa..8174690b517 100644 --- a/docs/manual/mod/mod_rewrite.xml +++ b/docs/manual/mod/mod_rewrite.xml @@ -1404,8 +1404,9 @@ cannot use $N in the substitution string! noescape|NE Prevent mod_rewrite from applying hexcode escaping of - special characters in the result of the rewrite. details ... + special characters in the result of rewrites that result in + redirection. + details ... nosubreq|NS diff --git a/docs/manual/rewrite/flags.xml b/docs/manual/rewrite/flags.xml index ce418d750fd..c199ee0f6c4 100644 --- a/docs/manual/rewrite/flags.xml +++ b/docs/manual/rewrite/flags.xml @@ -476,7 +476,8 @@ RewriteRule "(.*\.(jpg|gif|png))$" "http://images.example.com$1" [P,NC]
NE|noescape

By default, special characters, such as & and ?, for example, will be converted to their hexcode -equivalent. Using the [NE] flag prevents that from happening. +equivalent for rules that result in external redirects. +Using the [NE] flag prevents that from happening.

-- 2.47.2