Given something like this
LocationMatch ^/(foo|bar)
ProxyPass balancer://abc123/
ProxyPassReverse balancer://abc123/
...
LocationMatch
it is obvious the regexp ^/(foo|bar) is used to determine the correct
location container to use for a given request. But after this, what is it's
value for
when facing such a situation ? If I need to
have ProxyPassReverse understand a regex then it will not do so just
because I placed it outside of the LocationMatch container since it
*always* understands the path argument as literal string - or did I miss
anyhing when looking at the ProxyPassReverse
On 25 Sep 2013, at 10:06, Thomas Eckert wrote:
I'm facing the problem that I have to use ProxyPassReverse inside a
LocationMatch
Just a thought: could you hack a workaround with Header Edit?
In my concrete situation I have a LocationMatch container with a negative
lookahead which I need
