httpd-bugs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject DO NOT REPLY [Bug 47207] mod_proxy_balancer + mod_proxy_http does not consider 500 responses "Err"
Date Sun, 17 May 2009 17:52:10 GMT

--- Comment #5 from Bj <>  2009-05-17 10:52:09 PST ---
If possible, I would like mod_proxy_balancer to consider any 50x status code
from the backend (here, an HTTP backend via mod_proxy_http) an error, such that
the BalancerMember gets the Err status. (Retry attempts and intervals can
already be configured.) Perhaps a configuration directive for status codes that
should be considered errors by the balancer manager?

This leads to a question -- does mod_proxy_balancer + mod_proxy_http consider
anything but a connection failure (connection refused or closed in the middle
of the request) an error such that the Err flag gets set? What about a 503
response from the backend?

(If it does consider 503 as a severe enough error that it raises the Err flag,
then perhaps I could compose a work-around transforming 500 to 503 using
mod_rewrite on the backend -- although I do admit that this is not a clean or
appealing work-around, that its use is limited, and that 500 usually does fill
a much valid purpose -- to tell what went wrong, although it seldom does.)

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

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message