54 Commits

Author	SHA1	Message	Date
isaacs	025f9133bb	http: Don't try to destroy nonexistent sockets ... Fixes #3740 In the case of pipelined requests, you can have a situation where the socket gets destroyed via one req/res object, but then trying to destroy *another* req/res on the same socket will cause it to call undefined.destroy(), since it was already removed from that message. Add a guard to OutgoingMessage.destroy and IncomingMessage.destroy to prevent this error.	2013-04-22 10:38:14 -07:00
Timothy J Fontaine	951e0b69fa	http: split Client into _http_client.js	2013-04-17 00:08:28 +02:00
Timothy J Fontaine	6717fdccb4	http: move Server and ServerResponse out	2013-04-17 00:08:28 +02:00
Timothy J Fontaine	dc9f97b7b9	http: move OutgoingMessage into it's own file	2013-04-17 00:08:28 +02:00