[Bug 56925] New: ProxyErrorOverride=On causes workers in error state after 500 errors

[bu...@apache.org]

https://issues.apache.org/bugzilla/show_bug.cgi?id=56925

            Bug ID: 56925
           Summary: ProxyErrorOverride=On causes workers in error state
                    after 500 errors
           Product: Apache httpd-2
           Version: 2.4.10
          Hardware: All
                OS: Linux
            Status: NEW
          Severity: major
          Priority: P2
         Component: mod_proxy_balancer
          Assignee: bugs@httpd.apache.org
          Reporter: cristian.httpd@gmail.com

Consider the following setup for a reverse proxy. 

ProxyRequests Off
ProxyErrorOverride On
ProxyPass /error !
ErrorDocument 500 /error/500.html

ProxyPass / balancer://cluster/ nocanon
ProxyPassReverse / balancer://cluster/

<Proxy balancer://cluster>
    BalancerMember http://localhost:9001 route=node0 keepalive=On ping=3
retry=60 loadfactor=100
    BalancerMember http://localhost:9011 route=node1 keepalive=On ping=3
retry=60 loadfactor=100

    ProxySet stickysession=JSESSIONID|jsessionid lbmethod=byrequests timeout=90
nofailover=On
</Proxy>

If I generate a request for a buggy page that causes a 500 error, the worker
would be put in error state for one minute according to the retry parameter,
regardless if subsequent requests are successful. 

However, if I switch ProxyErrorOverride to Off, the worker would not be put in
error state after a request that generates a 500 error, and other clients can
still use the same worker.

Based on the documentation, if the failonstatus does not contain the 500 status
code the worker should not be put in error state in case of a single request
generating a 500 error.

-- 
You are receiving this mail because:
You are the assignee for the bug.

---------------------------------------------------------------------
To unsubscribe, e-mail: bugs-unsubscribe@httpd.apache.org
For additional commands, e-mail: bugs-help@httpd.apache.org