Return-Path: X-Original-To: apmail-trafficserver-users-archive@www.apache.org Delivered-To: apmail-trafficserver-users-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 286879246 for ; Mon, 9 Apr 2012 17:18:00 +0000 (UTC) Received: (qmail 32898 invoked by uid 500); 9 Apr 2012 17:17:59 -0000 Delivered-To: apmail-trafficserver-users-archive@trafficserver.apache.org Received: (qmail 32868 invoked by uid 500); 9 Apr 2012 17:17:59 -0000 Mailing-List: contact users-help@trafficserver.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: users@trafficserver.apache.org Delivered-To: mailing list users@trafficserver.apache.org Received: (qmail 32858 invoked by uid 99); 9 Apr 2012 17:17:59 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 09 Apr 2012 17:17:59 +0000 X-ASF-Spam-Status: No, hits=0.7 required=5.0 tests=SPF_NEUTRAL X-Spam-Check-By: apache.org Received-SPF: neutral (athena.apache.org: local policy) Received: from [71.6.165.248] (HELO kramer.ogre.com) (71.6.165.248) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 09 Apr 2012 17:17:52 +0000 Received: from [192.168.201.78] (homey.ogre.com [24.52.35.136]) (authenticated bits=0) by kramer.ogre.com (8.14.5/8.14.5) with ESMTP id q39HHSVx009894 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NOT); Mon, 9 Apr 2012 10:17:30 -0700 Message-ID: <4F8319A8.6090809@apache.org> Date: Mon, 09 Apr 2012 11:17:28 -0600 From: Leif Hedstrom User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:11.0) Gecko/20120327 Thunderbird/11.0.1 MIME-Version: 1.0 To: users@trafficserver.apache.org CC: Philip Subject: Re: Track down 400 error References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org On 4/9/12 11:04 AM, Philip wrote: > Hi, > > I have just started testing trafficserver in production but for some > reason my error log is full of such lines: > > 20120409.18h42m47s RESPONSE: sent 41.249.21.105 status > 400 (Invalid HTTP Request) for '/' > 20120409.18h42m48s RESPONSE: sent 88.231.146.188 status 400 (Invalid HTTP > Request) for '/' > 20120409.18h42m49s RESPONSE: sent 119.93.197.215 status 400 (Invalid HTTP > Request) for '/' > 20120409.18h42m50s RESPONSE: sent 94.120.152.153 status 400 (Invalid HTTP > Request) for '/' > 20120409.18h42m50s RESPONSE: sent 35.32.231.34 status 400 (Invalid HTTP > Request) for '/' > 20120409.18h42m52s RESPONSE: sent 75.147.253.45 status 400 (Invalid HTTP > Request) for '/' > 20120409.18h42m52s RESPONSE: sent 58.106.6.105 status 400 (Invalid HTTP > Request) for '/' > 20120409.18h42m52s RESPONSE: sent 80.216.110.194 status 400 (Invalid HTTP > Request) for '/' > 20120409.18h42m53s RESPONSE: sent 190.82.40.192 status 400 (Invalid HTTP > Request) for '/' > 20120409.18h42m53s RESPONSE: sent 213.151.57.111 status 400 (Invalid HTTP > Request) for '/' > 20120409.18h42m56s RESPONSE: sent 82.38.126.80 status 400 (Invalid HTTP > Request) for '/' > 20120409.18h42m58s RESPONSE: sent 189.153.63.57 status 400 (Invalid HTTP > Request) for '/' A *wild* guess is that these are clients disconnecting. I changed this error message on trunk to reflect that the client has disconnected instead of giving this error (the old code will try to "parse" the empty request line, and therefore gives that error). The new version (e.g. 3.1.3 or trunk) will detect the client disconnecting, and not try to parse the empty request. -- Leif