What if you use a non-chunked request? You asked already and the response was that TC basically doesn't handle chunked requests.
TC handles chunked requests in all ways except that it doesn't have a methodology in the servlet API (EOFException etc) for notifying you if you try to read beyond EOD. Chunking is a requirement of HTTP1.1.
TC appears at least from what I can tell. to always close the socket on completion of a request - unless I am missing some critical configuration item or doing something that disables it.
Anyone know where exactly what it does with keep-alive under what circumstances is documented? (Yes I know if I tackle the big job of understanding the source as if I wrote it I can figure it out) but I mean a "specification" that is a bit easier to get aquainted with :)
Thanks PK At 10:30 3/11/2007, you wrote:
Well, "Connection: close" is supposed to cause the server to close the connection after the request has been fulfilled, but it looks like your experience is that TC closes the connection no matter what. What if you use a non-chunked request? You asked already and the response was that TC basically doesn't handle chunked requests.
--------------------------------------------------------------------- To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
