On Mon, May 7, 2012 at 6:16 PM, Subbu Allamaraju <[email protected]> wrote: > Is it expected that applications using socket.setTimeout be prepared to > receive the 'timeout' event *after* getting a complete response (as though no > timeout occurred)? > > var clientReq = http.request(options, function (clientRes) { > // happy path > > }); > clientReq.setTimeout(function () { > // handle timeout > }); > clientReq.end(); > > I'm noticing that, under some load, 'timeout' events occasionally get fired > after a valid response. Is this expected behavior?
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. -- 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
