https://issues.apache.org/bugzilla/show_bug.cgi?id=57520
--- Comment #11 from dk <[email protected]> --- Your insistence was very much appreciated. It led me to re-check Jetty backend. Yes, I am not expecting zero error, just want to make sure the most obvious things to increase stability are implemented. In my case I believe retry=0 (with maxattempts=1000) is very proper since our Jetty restart script "staggers" restarts to ensure that only 1/3 of all servers may be down at a time (we take IP address modulo 3 to calculate the restart delay multiplier) - so there is always a server to fall back on. Just to confirm - if httpd encounters 503 from Jetty under this regime, would it retry a different balancer or return 503 to client (with failonstatus set)? The docs are not very clear on whether failonstatus would cause the requests to be retried and/or if this behavior could be configured... I am going to clean up our proxy settings per your advice. The ones I have now were result of trial and error with various suggestions from https://issues.apache.org/bugzilla/show_bug.cgi?id=37770 (e.g. I do not care about Expect header or HTTP 1.0). I am curious how much of the advice in that discussion thread is still applicable with 2.2.29 vs. may have been fixed / worked around? -- 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]
