Return-Path: Delivered-To: apmail-httpd-users-archive@www.apache.org Received: (qmail 64338 invoked from network); 20 May 2005 14:05:53 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 20 May 2005 14:05:53 -0000 Received: (qmail 25626 invoked by uid 500); 20 May 2005 14:05:30 -0000 Delivered-To: apmail-httpd-users-archive@httpd.apache.org Received: (qmail 25605 invoked by uid 500); 20 May 2005 14:05:30 -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 25575 invoked by uid 99); 20 May 2005 14:05:30 -0000 X-ASF-Spam-Status: No, hits=0.4 required=10.0 tests=DNS_FROM_RFC_ABUSE,RCVD_BY_IP,SPF_HELO_PASS,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (hermes.apache.org: domain of jslive@gmail.com designates 64.233.184.192 as permitted sender) Received: from wproxy.gmail.com (HELO wproxy.gmail.com) (64.233.184.192) by apache.org (qpsmtpd/0.28) with ESMTP; Fri, 20 May 2005 07:05:26 -0700 Received: by wproxy.gmail.com with SMTP id 67so824010wri for ; Fri, 20 May 2005 07:05:06 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=W58defXutDb3hnDi95Dks00RlHZPsKLJCyH7ttRhXnT1+Ac81twCTpxJTty3Gw0Abipa3RM9DstjUH3pEjZFMcri1wePqKq1IQSmZEvpcIv7IER8zFM99OWXMZyD63Qj7wtpIyTaDGgFJ+nA03OPY1RdiaGNayQoN8bo+LA1uKU= Received: by 10.54.81.12 with SMTP id e12mr1155525wrb; Fri, 20 May 2005 07:05:06 -0700 (PDT) Received: by 10.54.62.11 with HTTP; Fri, 20 May 2005 07:05:06 -0700 (PDT) Message-ID: Date: Fri, 20 May 2005 10:05:06 -0400 From: Joshua Slive Reply-To: Joshua Slive To: users@httpd.apache.org In-Reply-To: <722315B1300ED81181FF00D0B7478221022273E4@ntexchange01> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <722315B1300ED81181FF00D0B7478221022273E4@ntexchange01> X-Virus-Checked: Checked Subject: Re: [users@httpd] how does apache implement request forwarding X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N On 5/19/05, Michael Lu wrote: > When a request comes in does apache wait till the whole request body come= s > from the client then forward it to tomcat or apache forward the request a= s > soon as it receives the request header while the client is still > transferring the request body? > I ask this because we have EOFException from the tomcat side from time to > time when the client side applet try to send an object over the > URLConnection. And tomcat raises this exception around 5 mins later afte= r > it got the request. Timeout in httpd.conf is set to 300 secs. So my the= ory > is that apache closes its connection to client after timeout is reached a= nd > then raises the EOFException at the tomcat side. But my theory is invali= d > if apache forwards the request after it receive everything from the clien= t. I don't know the answer to your question, but I'm sure it depends on the method you use to connect apache httpd to tomcat (there are several choices). And I'm also sure that you'd get a more knowledgable crowd if you asked on a tomcat mailing list. Joshua. --------------------------------------------------------------------- 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