httpd-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jim Jagielski <...@jaguNET.com>
Subject Re: errors that cause proxy to move worker to error state
Date Tue, 31 Aug 2010 14:36:14 GMT

On Aug 31, 2010, at 10:24 AM, Jeff Trawick wrote:

> On Tue, Aug 31, 2010 at 9:58 AM, Rainer Jung <rainer.jung@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.pluem@vodafone.com <mailto:ruediger.pluem@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 prior request?).
> 
> So that could result in "close this backend connection" not "put into error state" as
a reaction, right?
> 
> Yes (I forgot or didn't know the distinction between closing a particular connection
and marking the worker in error)
> 
> At present we don't mark particular connections for close just based on the status code
without marking the worker in error, right?
> 
> Anyway, my question should have been
> 
> "Should we close backend connections if we get 400?"
> 

For now, yeah. Likely safer.


Mime
View raw message