https://issues.apache.org/bugzilla/show_bug.cgi?id=47207
--- Comment #5 from Bj <[email protected]> 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: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
