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

History

Alexis Campailla 527cabefcb test: fix connection reset in http test In this test, an HTTP server was ending the response before consuming all the data sent in the PUT request. Ending the response would cause the socket to be destroyed, and since there is some data still to be read, an ECONNRESET is surfaced on the client side, event though the client has already ended its side and even seen a 'finish' event. See: http://www.w3.org/Protocols/rfc2616/rfc2616-sec8.html#sec8.2.2 While it is certainly admissible for the server to send a response before consuming the entire request, it seems reasonable to expect that the server would close the connection afterwards and that the ECONNRESET would be raised on the client. So I have changed the test to wait until the entire request has been consumed before sending the response.		11 years ago
..
addons	addons: build and test examples	11 years ago
debugger	debug client: connect after child is ready	11 years ago
disabled	fixes #6031 spelling errors	12 years ago
fixtures	node: do not ever close stdio	11 years ago
gc	test: refactor to use common testcfg	11 years ago
internet	test: refactor to use common testcfg	11 years ago
message	node: do not print SyntaxError hints to stderr	11 years ago
pummel	Merge remote-tracking branch 'upstream/v0.10'	11 years ago
simple	test: fix connection reset in http test	11 years ago
testpy	addons: build and test examples	11 years ago
common.js	vm: don't copy Proxy object from parent context	11 years ago