ProxyPassMatch does not work

Bug #387708 reported by jh
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Apache2 Web Server
Invalid
Undecided
Unassigned
apache2 (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Binary package hint: apache2

ProxyPassMatch is being interpreted as ProxyPass.

Revision history for this message
Chuck Short (zulcss) wrote :

Which version or apache are you using and can you provide more details of your setup?

Thanks
chuck

Changed in apache2 (Ubuntu):
status: New → Incomplete
Revision history for this message
jh (jhiswin) wrote :

Ubuntu 9.04 Jaunty
Apache 2.2
a2enmod proxy_ajp

It seems that the documentation was recently fixed to show that ProxyPass(Match) is not meant to be used within Location declaratives. Either that or I misread or read the wrong docs, as I remember following docs that showed ProxyPass(Match) as being placed within Location declaratives.

Using ProxyPass(Match) within Location declaratives causes unexpected behavior (to the user), such that ProxyPass disables the use of RegEx within Location(Match) declaratives, and whereby ProxyPassMatch enables RegEx within Location(Match).

Here is a use case, where I am trying to proxy(AJP) .jsp extension urls to Apache Tomcat
<Location .+\.jsp$>
ProxyPassMatch ajp://localhost:8009/
ProxyPassReverse ajp://localhost:8009/
</Location>
Notice that ProxyPassMatch only takes one parameter. Also notice that removing "Match" will cause the RegEx to stop matching.

As someone who has used Apache in the past, I probably should have realized that Apache behaves this way due to the way Locations are parsed, but I had been trying to follow the docs I was reading as literally as I could.

Anyhow, this bug should probably be marked invalid.

jh (jhiswin)
Changed in apache2 (Ubuntu):
status: Incomplete → Invalid
Changed in apache2:
status: New → Confirmed
status: Confirmed → Invalid
Revision history for this message
Eric Mugo (kunadawa) wrote :

jh, what you encountered appears to have been a bug, alright. Please have a look at the workaround at the url below

https://issues.apache.org/bugzilla/show_bug.cgi?id=46665

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.