https://issues.apache.org/bugzilla/show_bug.cgi?id=56074
Bug ID: 56074
Summary: ProxyPassMatch-Rules break by upgrade from 2.4.4 to
2.4.6
Product: Apache httpd-2
Version: 2.4.6
Hardware: PC
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: mod_proxy
Assignee: [email protected]
Reporter: [email protected]
Hello,
i tried to upgrade an Apache 2.4.4 up to version 2.4.6 with the following
ProxyPassMatch-Rules:
ProxyPassMatch ^(.*\.jsp(?:;.*)?)$ balancer://appcluster$1
ProxyPassMatch ^(.*\.do(?:;.*)?)$ balancer://appcluster$1
ProxyPassMatch ^(.*/servlet/.*(?:;.*)?)$ balancer://appcluster$1
During the syntax check the Apache 2.4.6 failed with the following error:
ProxyPass unable to parse: ^(.*\\.jsp(?:;.*)?)$
By changing the order of the rules and putting the servlet rule in front the
other rules the Apache 2.4.6 starts without any problem:
ProxyPassMatch ^(.*/servlet/.*(?:;.*)?)$ balancer://appcluster$
ProxyPassMatch ^(.*\.jsp(?:;.*)?)$ balancer://appcluster$1
ProxyPassMatch ^(.*\.do(?:;.*)?)$ balancer://appcluster$1
I also found out the following bug for apache 2.2.x
https://issues.apache.org/bugzilla/show_bug.cgi?id=46665, which shows nearly
the same problem and recommends to change the rules i.e.
ProxyPassMatch ^/(.*\.jsp(?:;.*)?)$ balancer://appcluster$1
ProxyPassMatch ^/(.*\.do(?:;.*)?)$ balancer://appcluster$1
ProxyPassMatch ^(.*/servlet/.*(?:;.*)?)$ balancer://appcluster$1
the curious point here for me is, why does apache 2.4.6 break if an "incorrect"
match (in 2.4.4 the matches worked well, without any problems) is placed as
first match, but not as a follwoing match if the first one has an prefixed /
like ^(.*/servlet/.*(?:;.*)?)$.
Cheers,
André
--
You are receiving this mail because:
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
