Return-Path: Delivered-To: apmail-tomcat-dev-archive@www.apache.org Received: (qmail 99431 invoked from network); 1 Apr 2010 10:45:18 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 1 Apr 2010 10:45:18 -0000 Received: (qmail 932 invoked by uid 500); 1 Apr 2010 10:45:17 -0000 Delivered-To: apmail-tomcat-dev-archive@tomcat.apache.org Received: (qmail 601 invoked by uid 500); 1 Apr 2010 10:45:15 -0000 Mailing-List: contact dev-help@tomcat.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: "Tomcat Developers List" Delivered-To: mailing list dev@tomcat.apache.org Received: (qmail 592 invoked by uid 99); 1 Apr 2010 10:45:14 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 01 Apr 2010 10:45:14 +0000 X-ASF-Spam-Status: No, hits=-2000.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [140.211.11.9] (HELO minotaur.apache.org) (140.211.11.9) by apache.org (qpsmtpd/0.29) with SMTP; Thu, 01 Apr 2010 10:45:12 +0000 Received: (qmail 98970 invoked from network); 1 Apr 2010 10:44:50 -0000 Received: from unknown (HELO ?127.0.0.1?) (127.0.0.1) by 127.0.0.1 with SMTP; 1 Apr 2010 10:44:50 -0000 Message-ID: <4BB47921.8030101@apache.org> Date: Thu, 01 Apr 2010 06:44:49 -0400 From: Tim Funk User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1.9) Gecko/20100317 Thunderbird/3.0.4 MIME-Version: 1.0 To: Tomcat Developers List Subject: Re: Chunked encoding should be used also when not using keepalive References: <4BB4787A.9000600@apache.org> In-Reply-To: <4BB4787A.9000600@apache.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit X-Virus-Checked: Checked by ClamAV on apache.org Wait a sec ... not enough coffee. I might have answered a totally different question (and incorrectly too) -Tim On 4/1/2010 6:42 AM, Tim Funk wrote: > Doing this would be bad. When serving JSP's (or anything dynamic greater > than the buffer size) - the content length is not sent to the client. So > when the end of the request is sent - there is no signal to the client > to let them know the request is over and they can start a new request > over the same connection. > > With chunked encoded - we can get away with no content length header > because the each chunk as the length. > > -Tim > > On 4/1/2010 6:02 AM, �scar Fr�as Barranco wrote: >> Hello. >> >> Currently Tomcat HTTP 1.1 Connector disables the use of chunked >> encoding if >> keepalive is not used. This happens when an HTTP 1.1 request contains a >> "Connection: close" header. >> I propose to change Coyote to use chunked encoding (for HTTP 1.1) even if >> keepalive is disabled. --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org For additional commands, e-mail: dev-help@tomcat.apache.org