lukechilds/node - node - Gitea: Git with a cup of tea

8580 Commits

131 Branches

446 Tags

325 MiB

Tree: c188a75103

Commit Graph

Author SHA1 Message Date

Author	SHA1	Message	Date
Ben Noordhuis	d3ddee61c2	http: forward-port missing bits from `01e2920` Forward-port the comments from commit `01e2920` (v0.10) to the master branch. Everything else from that patch already exists in master. It didn't merge cleanly because lib/http.js has been split up in several files.	12 years ago
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.	12 years ago
Timothy J Fontaine	5909a9c9bd	http: move IncomingMessage into its own file	12 years ago

Ben Noordhuis

d3ddee61c2

http: forward-port missing bits from 01e2920

Forward-port the comments from commit 01e2920 (v0.10) to the master
branch. Everything else from that patch already exists in master.

It didn't merge cleanly because lib/http.js has been split up in
several files.

12 years ago

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.

12 years ago

Timothy J Fontaine

5909a9c9bd

http: move IncomingMessage into its own file

12 years ago

3 Commits (c188a7510317bfdaa19e87c6870c5ee7d965a6b9)