On Tue, May 9, 2017 at 4:08 AM, Michael Haas wrote:
> Is this a intended change?
There was a 2.4.25 regression, you commented on the bug. The change is
reverted and will be in the next release.
https://bz.apache.org/bugzilla/show_bug.cgi?id=60458
In the interim, I think all-or-nothing for Locati
Most specific proxypass directives take precedence over the most "global"
ones, while with Location is the opposite, you must define the most global
paths first and then the most specific.
So with ProxyPass the correct order or definition would be (if you define
/something later it will be ignored
i only updated apache + openssl from source.
The only thing i found what changed in 2.4.25 with proxypass and location
is this https://bz.apache.org/bugzilla/show_bug.cgi?id=60458
And i think this is the same problem which i have
http://stackoverflow.com/questions/43606856/apache2-configuration-vir
On Tue, 9 May 2017 10:08:36 +0200
Michael Haas wrote:
> With 2.4.25 all requests are routet through the last ProxyPass, the
> Location directive is ignored so the rewrite from the context is not
> happening.
> If i put the last ProxyPass in a Location directive like "^/(?!service)"> it's again
Hello, we upgraded from 2.4.18 to 2.4.25 and now our configuration
isn't working anymore.
ProxyPreserveHost On
BalancerMember http://xxx.xx.xx.xx:8080 route=vm_0 ping=5
BalancerMember http://xxx.xx.xx.xx:8080 route=vm_1 ping=5
ProxyPass balancer://ppp/system
stick
