]
Michal Karm Babacek moved JWS-436 to MODCLUSTER-505:
----------------------------------------------------
Project: mod_cluster (was: JBoss Web Server)
Key: MODCLUSTER-505 (was: JWS-436)
Workflow: GIT Pull Request workflow (was: CDW v1)
Component/s: Native (httpd modules)
(was: httpd)
Target Release: (was: JWS 3.0.3 GA)
Affects Version/s: 1.2.12.Final
1.3.2.Final
(was: JWS 3.0.2 GA)
Fix Version/s: 1.3.3.Final
1.2.13.Final
(was: JWS 3.0.3 CR1)
Release Notes Docs Status: (was: Documented as Known Issue)
ProxyErrorOverride=On causes workers in error state after 500
errors
---------------------------------------------------------------------
Key: MODCLUSTER-505
URL:
https://issues.jboss.org/browse/MODCLUSTER-505
Project: mod_cluster
Issue Type: Bug
Components: Native (httpd modules)
Affects Versions: 1.2.12.Final, 1.3.2.Final
Reporter: Aaron Ogburn
Assignee: Jean-Frederic Clere
Fix For: 1.3.3.Final, 1.2.13.Final
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.