Ok, I do now understand ... Thank you very much and sorry for the fright ! ;-)
Last thing I'd like to confirm : When data is sent over a socket, it will fill the socket buffer (at the client side) and then sending of data will block until the server side reads from the socket buffer ? If the server closes the socket and there is data in the socket buffer, on the client side, the client socket will report an exception. Is that correct ? Thanks. -Vincent BTW, I've tried reading the body with getParameter() and effectively the error does not happen any more. > -----Original Message----- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] > Sent: 07 February 2002 22:47 > To: Tomcat Developers List > Subject: RE: Tomcat 3.3 - Cactus Issue > > On Thu, 7 Feb 2002, Larry Isaacs wrote: > > > Many thanks for finding this. Not suprisingly Costin's > > initial guess was correct. Fortunately I wasn't wrong > > about one assumption, which was the reason for the failure > > was that Tomcat 3.3 was too fast. Thanks again, to Costin. > > Well, given the amount of time I had to spend to fix > the CRLF POST bug, it's not something I'll forget soon. > It's not often that you get to look with tcpdump at > each packet for a week and get back to the tcp spec. > > I had a bit of panic when I saw this problem - it's > very painful to debug this kind of problems, and my hope > was that I finally understood how tcp works... > > BTW, we should keep the sleep() as an option - it's > scarry that tomcat is processing the request faster than > the OS can send data... We need to add at least 100ms > to each request. > > > Costin > > > -- > To unsubscribe, e-mail: <mailto:tomcat-dev- > [EMAIL PROTECTED]> > For additional commands, e-mail: <mailto:tomcat-dev- > [EMAIL PROTECTED]> > -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
