Mailing-List: contact dev-help@httpd.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@httpd.apache.org
Received-SPF: pass (athena.apache.org: domain of covener@gmail.com designates
 209.85.128.173 as permitted sender)
MIME-Version: 1.0
In-Reply-To: 
 <CAPV0b05_fke+QBZRNHESmsUM16BdrKkb1MAWx0wOBT7chsmHQQ@mail.gmail.com>
References: 
 <CAPV0b05_fke+QBZRNHESmsUM16BdrKkb1MAWx0wOBT7chsmHQQ@mail.gmail.com>
Date: Tue, 7 May 2013 08:08:24 -0400
Message-ID: 
 <CALK=YjPMJCBwzx_PvStyLAuSXRrOX0aL7QxkPmPf7tfdn0m87w@mail.gmail.com>
Subject: Re: Improve mod_proxy's error marking of workers
From: Eric Covener <covener@gmail.com>
To: dev@httpd.apache.org
Content-Type: text/plain; charset=ISO-8859-1

On Tue, May 7, 2013 at 6:24 AM, Thomas Eckert
<thomas.r.w.eckert@gmail.com> wrote:
> Attached patch contains a directive to improve the error marking of workers.
> Basically, some errors will cause a worker to be marked as "in error" while
> others don't. I can't see a reason for this so I added a directive to have
> all errors mark the error correctly - especially useful for automated
> systems using mod_proxy to check if the system is healthy.

I think you need to screen out 4xx at least to prevent client errors
from marking down your backends.