tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Bill Barker" <wbar...@wilshire.com>
Subject Re: TCK Issue with Tomcat 5.5.12
Date Thu, 22 Dec 2005 21:11:19 GMT

"Bill Stoddard" <bill@wstoddard.com> wrote in message 
news:43AB0E1A.9070700@wstoddard.com...
> Remy Maucherat wrote:
>> Bill Stoddard wrote:
>>
>>> 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.
>>
>>
>> It's a HTTP/1.0 request. Is that still true ?
>>
>
> Yes, HTTP/1.1 servers can handle HTTP/1.0 requests.  Here's an experiment 
> to try.
> telnet www.apache.org 80
> then type in:
> POST /foo/bar HTTP/1.0
> <enter>
> <enter>
>
> watch what happens. Apache httpd handles the request properly.
>

Tomcat handles it much the same way for for a 404 ;-).

However, I'm guessing that Httpd sets up an EOS-only bucket-brigade (but am 
not interested enough to look it up :), so that if the target existed and 
tried to read the body they would just get EOS.

Given that the request is malformed under RFC1945, so Tomcat probably should 
do the same thing (which is basically what Remy's patch does).

> Bill 




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


Mime
View raw message