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 7EBE66890 for ; Mon, 16 May 2011 16:08:03 +0000 (UTC) Received: (qmail 98197 invoked by uid 500); 16 May 2011 16:08:00 -0000 Delivered-To: apmail-httpd-users-archive@httpd.apache.org Received: (qmail 98107 invoked by uid 500); 16 May 2011 16:08:00 -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 98099 invoked by uid 99); 16 May 2011 16:08:00 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 16 May 2011 16:08:00 +0000 X-ASF-Spam-Status: No, hits=0.0 required=5.0 tests=FREEMAIL_FROM,SPF_PASS,T_TO_NO_BRKTS_FREEMAIL X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of lists@nabble.com designates 216.139.236.26 as permitted sender) Received: from [216.139.236.26] (HELO sam.nabble.com) (216.139.236.26) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 16 May 2011 16:07:55 +0000 Received: from isper.nabble.com ([192.168.236.156]) by sam.nabble.com with esmtp (Exim 4.69) (envelope-from ) id 1QM0KU-0007lX-V4 for users@httpd.apache.org; Mon, 16 May 2011 09:07:34 -0700 Message-ID: <31630537.post@talk.nabble.com> Date: Mon, 16 May 2011 09:07:34 -0700 (PDT) From: cbmg0507 To: users@httpd.apache.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Nabble-From: curt.gabes@gmail.com Subject: [users@httpd] ReadTimeout but Apache shows transaction successful Hoping that someone may have seen this before. We have Apache setup as a reverse proxy behind the public public internet. Very basic setup. Clients connect from the public internet through firewall to the Apache HTTP server that is reverse proxying the requests to our application servers. Intermittently, we see a situation where the client reports a connect or read timeout exception. In all cases, the Apache log shows the transaction processed, returned a 200 status code and completed within a second or two. I'm not suggesting that its an Apache problem, but wondering, generally if anyone else has seen this and is there anything I can do to help alleviate? Seems strange that the client waits longer than what Apache is reporting it took for it to process, that is reports sending back the response but the client never got it. Thanks to anyone... -- View this message in context: http://old.nabble.com/ReadTimeout-but-Apache-shows-transaction-successful-tp31630537p31630537.html Sent from the Apache HTTP Server - Users mailing list archive at Nabble.com. --------------------------------------------------------------------- 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