httpd-bugs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject [Bug 53651] New: Worker failure doesn't have same behaviour as worker connection failure
Date Fri, 03 Aug 2012 16:46:02 GMT
https://issues.apache.org/bugzilla/show_bug.cgi?id=53651

          Priority: P2
            Bug ID: 53651
          Assignee: bugs@httpd.apache.org
           Summary: Worker failure doesn't have same behaviour as worker
                    connection failure
          Severity: normal
    Classification: Unclassified
                OS: Linux
          Reporter: david.newcomb@bigsoft.co.uk
          Hardware: PC
            Status: NEW
           Version: 2.4.2
         Component: mod_proxy
           Product: Apache httpd-2

The documentation for failonstatus
(http://httpd.apache.org/docs/2.4/mod/mod_proxy.html) states that the behaviour
will be the same as other worker errors and this is not the case.
===

Platform: Apache 2.4.2 on CentOS under VirtualBox

Apache mod_proxy & mod_proxy_balancer with 2 IIS boxes running a .net
application. When application is not running but IIS is, then IIS (correctly)
returns 500 error code responses for requests directed at the application.

If I switch off IIS so Apache can't connect mod_proxy_balancer (or something)
puts the other machine into error state and automatically retries another
worker.
If I switch IIS back on so that it starts returning 500 error statuses the
failonstatus detects the failure and places the worker machine into error state
however it throws that failure back up the call stack to the client so that the
client gets proxy error from apache.

The documentation for failonstatus
(http://httpd.apache.org/docs/2.4/mod/mod_proxy.html) states that the behaviour
will be the same as other worker errors and this is not the case.

My config ( but it's pretty standard ...and it's a test environment! ):

ProxyRequests Off
<Proxy *>
        Order deny,allow
        Allow from all
</Proxy>

<Proxy balancer://qtube>
        # 500 Internel server error
        # 501 Not implemented ( need to throw back to client )
        # 502 Bad Gateway. The proxy server received an invalid response from
an upstream server
        # 503 Service unavailable

        ProxySet lbmethod=byrequests failonstatus=500,502,503

        BalancerMember http://10.165.250.201:80/mydir connectiontimeout=1
timeout=5 retry=30
        BalancerMember http://10.165.250.206:80/mydir connectiontimeout=1
timeout=5 retry=30

        Order deny,allow
        Allow from all

</Proxy>

<Location /mydir>
        ProxyPass balancer://qtube
        ProxyPassReverse balancer://qtube
        Order allow,deny
        Allow from all
</Location>

<Location /balancer-manager>
        SetHandler balancer-manager

        Order deny,allow
        Allow from all
</Location>

-- 
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


Mime
View raw message