https://bz.apache.org/bugzilla/show_bug.cgi?id=59869
Bug ID: 59869
Summary: mod_proxy failonstatus option is broken since 2.4.17
on Solaris 10
Product: Apache httpd-2
Version: 2.4.23
Hardware: All
OS: Solaris
Status: NEW
Severity: regression
Priority: P2
Component: mod_proxy
Assignee: [email protected]
Reporter: [email protected]
Configuration:
<Proxy "balancer://cluster">
BalancerMember "http://localhost:17293/webapp"; route=node1 retry=10 ping=1
connectiontimeout=1
BalancerMember "http://localhost:17294/webapp"; route=node2 retry=10 ping=1
connectiontimeout=1
</Proxy>
ProxyPass / "balancer://cluster/" stickysession=JSESSIONID|jsessionid
failonstatus=502,503
For 2.4.16 and later versions, when backend node returns 503, Apache forces it
into error state.
Since 2.4.17 till 2.4.23, when 503 returned, nothing happens, node status is OK
and Apache keep on proxying requests on this node
This behavior is reproduced both on Sparc machine and x86 VirtualBox VM
--
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]
