Mailing-List: contact dev-help@httpd.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@httpd.apache.org
Received-SPF: pass (nike.apache.org: domain of trawick@gmail.com designates
 209.85.215.173 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:in-reply-to:references:date:message-id:subject:from:to
         :content-type:content-transfer-encoding;
        b=xgVTGKi+xDw+HaObdAL8UqJIq+UyW51CekyTnNSX1Jp4+qEdhL07jqY/BrSfWmqwAK
         ykPEUwMfYBUC4goMG/VKuGqhb0C61v/XOneLTtQ+z99e2KUGMw552AbB7BTzktZDFCVs
         l2xB5RvkiSFTOXFLSa6i8eaVINrESpnDFG8xM=
MIME-Version: 1.0
In-Reply-To: <20101112232203.62e99611@baldur>
References: <20101112232203.62e99611@baldur>
Date: Sat, 13 Nov 2010 07:28:42 -0500
Message-ID: <AANLkTim9EzxnWmU0OK_2WiynW+xa=LOBe1_CeNwcku+R@mail.gmail.com>
Subject: Re: Error returned on broken chunking
From: Jeff Trawick <trawick@gmail.com>
To: dev@httpd.apache.org
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

On Fri, Nov 12, 2010 at 6:22 PM, Nick Kew <nick@webthing.com> wrote:
> I've just been failing to diagnose someone on IRC's problem
> with httpd returning 503 (Service Unavailable).
>
> A look at the source turns up just one usage outside the
> script and proxy paths: in ap_http_filter, it returns
> SERVICE_UNAVAILABLE on encountering a chunked encoding error.
> This looks like a bug to me: surely that should return 400
> on bad request from the client.
>
> The other case would be reading broken chunking coming from
> a backend when 502 (not 503) looks correct. =A0But that's
> only really useful for logging, as it's unlikely to be
> encountered before the response status has been sent
> down the wire.
>
> Any strong rationale for 503, or should I just change
> it to 400?

change it