Hi Dave thanks for replying Does this mean that when a request comes in, Apache doesn't hand off the request to Mongrel until it has received the entirety of the request? If not, how does Apache know the connection has been closed/client has stopped sending data.
I thought it worked (roughly) like: 1 Apache receives beginning of request (Content-length headers and so on) 2 Apache forwards request to Mongrel 3 Mongrel begins reading request (in my case uploading a 3 MB file over a slow connection) In the above scenario, if the client stopped sending data, would it not be Mongrel that raised the error? Thanks very much! Dave Cheney wrote: > Hi Matt, > > I believe that this error is reported when the client stops sending > data. If you grep through the sources the area that generates this > error is still related to the request. For us, this was a clue that > eventually pointed to a duplex mismatch upstream from our rack that > was causing tcp connections to collapse under heavy traffic. > > Cheers > > Dave -- Posted via http://www.ruby-forum.com/. _______________________________________________ Mongrel-users mailing list Mongrel-users@rubyforge.org http://rubyforge.org/mailman/listinfo/mongrel-users