Return-Path: X-Original-To: apmail-httpd-users-archive@www.apache.org Delivered-To: apmail-httpd-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 C770043DD for ; Mon, 9 May 2011 19:02:38 +0000 (UTC) Received: (qmail 8177 invoked by uid 500); 9 May 2011 19:02:33 -0000 Delivered-To: apmail-httpd-users-archive@httpd.apache.org Received: (qmail 8091 invoked by uid 500); 9 May 2011 19:02:33 -0000 Mailing-List: contact users-help@httpd.apache.org; run by ezmlm Precedence: bulk Reply-To: users@httpd.apache.org list-help: list-unsubscribe: List-Post: List-Id: Delivered-To: mailing list users@httpd.apache.org Received: (qmail 8083 invoked by uid 99); 9 May 2011 19:02:33 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 09 May 2011 19:02:33 +0000 X-ASF-Spam-Status: No, hits=-0.7 required=5.0 tests=RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of trafx@trafx.net designates 209.85.218.45 as permitted sender) Received: from [209.85.218.45] (HELO mail-yi0-f45.google.com) (209.85.218.45) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 09 May 2011 19:02:26 +0000 Received: by yib19 with SMTP id 19so2561838yib.18 for ; Mon, 09 May 2011 12:02:06 -0700 (PDT) Received: by 10.100.28.24 with SMTP id b24mr4614642anb.168.1304967726063; Mon, 09 May 2011 12:02:06 -0700 (PDT) MIME-Version: 1.0 Received: by 10.100.96.14 with HTTP; Mon, 9 May 2011 12:01:46 -0700 (PDT) From: TRAFx Research Date: Mon, 9 May 2011 13:01:46 -0600 Message-ID: To: users@httpd.apache.org Content-Type: text/plain; charset=ISO-8859-1 Subject: [users@httpd] Dropped packets and 408 responses Hello everyone, We've got a customer that's got a flakey network that's dropping packets. This has resulted in a few weird errors coming out of our Apache setup that I'm trying to work out if I can tweak to avoid. The sequence of events is essentially: 1) Client issues a POST from a file upload form. All headers arrive in the first packet, but no request body yet. 2) There is a pause of 10 seconds, no further data arrives 3) Apache issues a "302 Found" response 4) A few seconds later, we finally get packets for the original request body, flagged as TCP retransmissions, so the originals were sent, but got lost 5) Apache now complains with "501 Invalid Method" and this is what our customer ends up seeing in their browser. Issue 47087 (https://issues.apache.org/bugzilla/show_bug.cgi?id=47087) explains why I get the 501 at the end (fallback to HTTP/0.9) The question is, why is Apache returning the "302 Found" response rather than a "408 Client timeout" in step 3? The POST issued in step 1 has the appropriate Content-Length header. The timing of the "302 Found" response doesn't seem to align with the values of "Timeout" or "KeepAliveTimeout" that I have configured (15 sec and 300 sec). Has anyone seen this sequence of events before and knows a workaround to avoid it? daniel --------------------------------------------------------------------- The official User-To-User support forum of the Apache HTTP Server Project. See for more info. To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org " from the digest: users-digest-unsubscribe@httpd.apache.org For additional commands, e-mail: users-help@httpd.apache.org