errors that cause proxy to move worker to error state

2010-08-31 Thread Jeff Trawick
It looks like this is just 500 and 503. Why not 400, for example? if (access_status == OK) break; else if (access_status == HTTP_INTERNAL_SERVER_ERROR) { /* Unrecoverable server error. * We can not failover to another worker. *

Re: errors that cause proxy to move worker to error state

2010-08-31 Thread Andrew Oliver
A 400 doesn't indicate a problem with the worker or the system behind the proxy, it indicates a problem with the client. Also marking a worker bad for say a 401 unauthorized would make all authentication impossible, a 403 or 404 would drain the pool every time someone asked for something they

RE: errors that cause proxy to move worker to error state

2010-08-31 Thread Plüm, Rüdiger, VF-Group
A 400 does not mean that the backend is not available. It just means that a bad request was sent. In addition to what is directly delivered from the backend the proxy code itself uses 500 and 503 to signal the balancer code that the error it faced (in case there was no response code from the

Re: errors that cause proxy to move worker to error state

2010-08-31 Thread Jeff Trawick
On Tue, Aug 31, 2010 at 9:33 AM, Andrew Oliver acoli...@gmail.com wrote: A 400 doesn't indicate a problem with the worker or the system behind the proxy, it indicates a problem with the client. It could indicate that proxy is confused about what it sent though (in the presence of some

Re: errors that cause proxy to move worker to error state

2010-08-31 Thread Jeff Trawick
On Tue, Aug 31, 2010 at 9:40 AM, Plüm, Rüdiger, VF-Group ruediger.pl...@vodafone.com wrote: A 400 does not mean that the backend is not available. agreed It just means that a bad request was sent. I don't like that part ;) Maybe mod_proxy mangled what got sent (sent too much body on

Re: errors that cause proxy to move worker to error state

2010-08-31 Thread Rainer Jung
On 31.08.2010 15:44, Jeff Trawick wrote: On Tue, Aug 31, 2010 at 9:40 AM, Plüm, Rüdiger, VF-Group ruediger.pl...@vodafone.com mailto:ruediger.pl...@vodafone.com wrote: A 400 does not mean that the backend is not available. agreed It just means that a bad request was sent. I

Re: errors that cause proxy to move worker to error state

2010-08-31 Thread Jeff Trawick
On Tue, Aug 31, 2010 at 9:58 AM, Rainer Jung rainer.j...@kippdata.dewrote: On 31.08.2010 15:44, Jeff Trawick wrote: On Tue, Aug 31, 2010 at 9:40 AM, Plüm, Rüdiger, VF-Group ruediger.pl...@vodafone.com mailto:ruediger.pl...@vodafone.com wrote: A 400 does not mean that the backend is not

RE: errors that cause proxy to move worker to error state

2010-08-31 Thread Plüm, Rüdiger, VF-Group
From: Jeff Trawick [mailto:traw...@gmail.com] Sent: Dienstag, 31. August 2010 16:25 To: dev@httpd.apache.org Subject: Re: errors that cause proxy to move worker to error state On Tue, Aug 31, 2010 at

Re: errors that cause proxy to move worker to error state

2010-08-31 Thread Jim Jagielski
On Aug 31, 2010, at 10:24 AM, Jeff Trawick wrote: On Tue, Aug 31, 2010 at 9:58 AM, Rainer Jung rainer.j...@kippdata.de wrote: On 31.08.2010 15:44, Jeff Trawick wrote: On Tue, Aug 31, 2010 at 9:40 AM, Plüm, Rüdiger, VF-Group ruediger.pl...@vodafone.com mailto:ruediger.pl...@vodafone.com