Mailing-List: contact dev-help@tomcat.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Tomcat Developers List" <dev@tomcat.apache.org>
Received-SPF: pass (hermes.apache.org: local policy)
Message-ID: <43AB07A0.7020409@wstoddard.com>
Date: Thu, 22 Dec 2005 15:08:00 -0500
From: Bill Stoddard <bill@wstoddard.com>
Reply-To: bill@wstoddard.com
User-Agent: Mozilla Thunderbird 1.0.7 (Windows/20050923)
MIME-Version: 1.0
To: Tomcat Developers List <dev@tomcat.apache.org>
Subject: Re: TCK Issue with Tomcat 5.5.12
References: <0F56CBAD-618E-4068-A91C-6E84CA37FB77@gmail.com>
 <dodi1r$fl9$1@sea.gmane.org> <43AA7761.70301@apache.org>
In-Reply-To: <43AA7761.70301@apache.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Remy Maucherat wrote:
> Bill Barker wrote:
> 
>>> AFAICT, this code is assuming that there will always be a message  
>>> body in the POST Request. However, this is not necessarily the case  
>>> (and is certainly not true for the problem at hand). Eventually, 
>>> SocketInputStream.read() is called from within 
>>> o.a.coyote.http11.InternalReadBuffer.fill(). This call will throw a 
>>> SocketTimeoutException.
>>>
>>
>>
>> Then the test is broken.  It should either have a 'Content-Length: 0' 
>> header or a 'Transfer-Encoding: chunked' header with a '0' content 
>> delimater.  

Nope, that's incorrect.
 From RFC2616, the official HTTP standard definition:

    The presence of a message-body in a request is signaled by the
    inclusion of a Content-Length or Transfer-Encoding header field in
    the request's message-headers.

A bodyless POST request w/o a TE or CL header field is permitted by RFC2616. Of course, if the POST really 
does have a body, then bad things are guaranteed to happen.

> 
> Or it could close the input of the socket (note: nobody should be crazy 
> enough to use this method, though, as I suppose it won't work in many 
> cases). 

Nope, that technique won't work. The server can close the connection to signal the client that it's done 
sending a response body, but the client cannot use the same technique to signal the server that it has 
completed sending a request body.

Hope this helps.

Bill


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org