[mod_cluster-issues] [JBoss JIRA] (MODCLUSTER-505) ProxyErrorOverride=On causes workers in error state after 500 errors
RH Bugzilla Integration (JIRA)
issues at jboss.org
Mon May 30 13:54:00 EDT 2016
[ https://issues.jboss.org/browse/MODCLUSTER-505?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
RH Bugzilla Integration updated MODCLUSTER-505:
-----------------------------------------------
Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1309598 (was: https://bugzilla.redhat.com/show_bug.cgi?id=1338664, https://bugzilla.redhat.com/show_bug.cgi?id=1309598, https://bugzilla.redhat.com/show_bug.cgi?id=1310582)
> 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.3.2.Final, 1.2.12.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.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
More information about the mod_cluster-issues
mailing list