[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
Thu Aug 18 11:42:01 EDT 2016
[ https://issues.jboss.org/browse/MODCLUSTER-505?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13280974#comment-13280974 ]
RH Bugzilla Integration commented on MODCLUSTER-505:
----------------------------------------------------
Michal Karm Babacek <mbabacek at redhat.com> changed the Status of [bug 1338664|https://bugzilla.redhat.com/show_bug.cgi?id=1338664] from MODIFIED to VERIFIED
> 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.2.14.Final, 1.3.4.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