On May 7, 2012, at 11:32 AM, Ben Noordhuis wrote: > Maybe. It's possible that the server sends an incomplete response like > forgetting to set a Content-Length header, thereby forcing the client > to keep reading until the connection closes. > > On the other hand, if you've seen 'end' and 'close' events on the > request object, you might be looking at a bug in Node.
I'm seeing 'timeout' events occur after the 'end' event as well. I will open an issue. Given that the docs talk about "milliseconds of inactivity on the socket", idle timeout events once the parser is reading the stream may be confusing though. Subbu -- Job Board: http://jobs.nodejs.org/ Posting guidelines: https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines You received this message because you are subscribed to the Google Groups "nodejs" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/nodejs?hl=en?hl=en
