-
Bug
-
Resolution: Done
-
Major
-
1.3.2.Final, 1.2.12.Final
-
None
-
-
Documentation (Ref Guide, User Guide, etc.), Release Notes
-
Workaround Exists
-
-
When a VirtualHost uses ProxyPass to proxy traffic to the backend and uses ProxyErrorOverride to host custom error pages on Apache httpd side, when the backend replies with a 50x error code mod_proxy/mod_cluster marks that worker as down, breaking session stickiness. This behaviour is quite similar to have failonstatus=500 for example.
- clones
-
JWS-362 ProxyErrorOverride=On causes workers in error state after 500 errors
- Closed