[mod_cluster-issues] [JBoss JIRA] (MODCLUSTER-505) ProxyErrorOverride=On causes workers in error state after 500 errors

[RH Bugzilla Integration (JIRA)]

    [ https://issues.jboss.org/browse/MODCLUSTER-505?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13381393#comment-13381393 ] 

RH Bugzilla Integration commented on MODCLUSTER-505:
----------------------------------------------------

errata-xmlrpc <errata-xmlrpc at redhat.com> changed the Status of [bug 1310582|https://bugzilla.redhat.com/show_bug.cgi?id=1310582] from VERIFIED to RELEASE_PENDING

>  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.5.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
(v7.2.3#72005)