wi wrote:
Hi all
Our site is upgrading from 2.2.8 to 2.2.11, and we're getting some
unexpected behaviour.
Our current configuration makes heavy use of the [NE] flag. For instance
RewriteRule ^/(.*) balancer://delta/$1 [P,NE,L]
However, in the upgraded server the [NE] no longer appears to be
supported. I found the following line in the 2.2.10 changelog:
*) mod_rewrite: Preserve the query string when [proxy,noescape]. PR 45247.
[Tom Donovan]
The problem for us is that some requests we receive have already been
escaped. Is there a way we can get the old behaviour back?
The fix for PR 45247 shouldn't change how the characters in URIs are escaped.The query string portion of the URI was being dropped with [NE]. This fix ensures that the (unescaped) query string is retained in the URI when [NE] is used.
http://svn.apache.org/viewvc?view=rev&revision=683813Do you have an example of a URL which is getting escaped with your RewriteRule in 2.2.11, but was not escaped in 2.2.8? Setting the directives 'RewriteLog file-path' and 'RewriteLogLevel 9' should show how mod_rewrite manipulates your URI.
http://httpd.apache.org/docs/2.2/mod/mod_rewrite.html#rewritelog -tom- --------------------------------------------------------------------- The official User-To-User support forum of the Apache HTTP Server Project. See <URL:http://httpd.apache.org/userslist.html> for more info. To unsubscribe, e-mail: users-unsubscribe@xxxxxxxxxxxxxxxx " from the digest: users-digest-unsubscribe@xxxxxxxxxxxxxxxx For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx
|