Best practices for ProxyPassReverse

["Francisco Gimeno" <kikov@xxxxxxxxx>]

Hello,

I'm having some problems with ProxyPassReverse directive.

My current config is similar to this:

--------

<Location /A>
      ProxyPass http://B
      ProxyPass http://B
</Location>

<Location /C>
      ProxyPass http://B/C
      ProxyPass http://B/C
</Location>

---------

If I do the following test:
##########TEST1##########
$ telnet ReverseProxyIP 80
GET /C/ HTTP/1.1
Host: REVERSEHOST

HTTP/1.1 302 Found
Date: Mon, 12 May 2008 17:39:58 GMT
Server: Apache/2.0.61 (Unix) mod_ssl/2.0.61 OpenSSL/0.9.8e DAV/2 mod_jk/1.2.25 PHP/4.4.7
Location: http://REVERSEHOST/A/C/www/

---------
I was waiting a http://REVERSHOST/C/www

The same request to the internal server:
##########TEST2##########
$ telnet B 80
Trying XXXXXXXXXXX...
Connected to B.
Escape character is '^]'.
GET /C/ HTTP/1.1
Host: B

HTTP/1.1 302 Found
Date: Mon, 12 May 2008 17:42:30 GMT
Server: Apache/2.0.61 (Unix) mod_ssl/2.0.61 OpenSSL/0.9.8e DAV/2 mod_jk/1.2.25 PHP/4.4.7
Location: http://B/C/www
-------------

So, in TEST1 I expected a "Location: http://REVERSEHOST/C/www" without the A.

I tried to remove the ProxyPassReverse from <Location /A> and then it works as expected, so it seems they're interferring in some way.
It seems that ProxyPassReverse doesn't  pay attention that it should match the same <Location> than the Request.

is this a known bug?