Mailing-List: contact dev-help@httpd.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@httpd.apache.org
Message-ID: <3C22BC93.3080900@pacbell.net>
Date: Thu, 20 Dec 2001 20:37:39 -0800
From: Brian Pane <bpane@pacbell.net>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US;
 rv:0.9.5) Gecko/20011011
MIME-Version: 1.0
To: dev@httpd.apache.org
Subject: Re: read errors in 2.0.30
References: <3C22671A.1C1611CE@remulak.net>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit

Greg Ames wrote:

>httpd 2.0.30-dev was in production for about 11 minutes on daedalus. 
>Then I noticed a bunch of unusual errors in the log, so I moved us back
>to 2_0_28.  
>
>They all seem to deal with reading lines from the input filters.  There
>were 85 "request failed: error reading the headers" logs in 11 minutes,
>compared to just 8 on 2_0_28 so far today.  There were a lot of
>complaints about methods and URIs, with some funky stuff printed out as
>the request:
>

I just committed a fix for this.  My ap_rgetline() code didn't
properly handle a request line that arrived in multiple pieces.
Sorry about that.  The bug never showed up in testing before because
it's rare for a request line to get split between two packets when
using tools like ab on a local network.

--Brian