Bug 51987

Summary: RewriteRule doesn't work correctly with apache 2.3.
Product: Apache httpd-2 Reporter: gits
Component: mod_rewriteAssignee: Apache HTTPD Bugs Mailing List <bugs>
Status: RESOLVED LATER    
Severity: normal Keywords: MassUpdate
Priority: P2    
Version: 2.3.12-beta   
Target Milestone: ---   
Hardware: PC   
OS: Linux   

Description gits 2011-10-07 04:37:39 UTC
Hello.

I have an Apache with the following configuration.

ServerName hogehoge
<VirtualHost *:80>
  <LocationMatch "/service_a/*">
    RewriteEngine on
    RewriteRule /service_a/(.*) http://192.168.56.11/$1 [P]
  </LocationMatch>
  <LocationMatch "/service_b/*">
    RewriteEngine on
    RewriteRule /service_b/(.*) http://192.168.56.12/$1 [P]
  </LocationMatch>
</VirtualHost>

Thus the request URL shuold be rewrite:

http://hogehoge/service_a/foo1.html ==> http://192.168.56.11/foo1.html
http://hogehoge/service_b/foo2.html ==> http://192.168.56.12/foo2.html

However, it doesn't work correctly.
According to packet capture, the following accesses have sometimes occurred. 

http://hogehoge/service_a/foo1.html ==> http://192.168.56.12/foo1.html
http://hogehoge/service_b/foo2.html ==> http://192.168.56.11/foo2.html


Thanks you.
Comment 1 Eric Covener 2011-10-07 11:46:03 UTC
is your config paraphrased or verbatim? your locationmatch has what seems to be an erroneous regex, and is unnecessary given the rewriterule content.

Also:

"Although rewrite rules are syntactically permitted in <Location> and <Files> sections, this should never be necessary and is unsupported."

You'll have to capture your scenario in with trace level logging of mod_rewrite to make a convincing case for a bug.
Comment 2 William A. Rowe Jr. 2018-11-07 21:08:21 UTC
Please help us to refine our list of open and current defects; this is a mass update of old and inactive Bugzilla reports which reflect user error, already resolved defects, and still-existing defects in httpd.

As repeatedly announced, the Apache HTTP Server Project has discontinued all development and patch review of the 2.2.x series of releases. The final release 2.2.34 was published in July 2017, and no further evaluation of bug reports or security risks will be considered or published for 2.2.x releases. All reports older than 2.4.x have been updated to status RESOLVED/LATER; no further action is expected unless the report still applies to a current version of httpd.

If your report represented a question or confusion about how to use an httpd feature, an unexpected server behavior, problems building or installing httpd, or working with an external component (a third party module, browser etc.) we ask you to start by bringing your question to the User Support and Discussion mailing list, see [https://httpd.apache.org/lists.html#http-users] for details. Include a link to this Bugzilla report for completeness with your question.

If your report was clearly a defect in httpd or a feature request, we ask that you retest using a modern httpd release (2.4.33 or later) released in the past year. If it can be reproduced, please reopen this bug and change the Version field above to the httpd version you have reconfirmed with.

Your help in identifying defects or enhancements still applicable to the current httpd server software release is greatly appreciated.