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

Author	SHA1	Message	Date
Julien Gilli	0565d52a71	tests: don't assume IPv4 only in remote addr tests Tests in test-net-remote-address-port.js assume that client and server sockets always use IPv4. However, depending on the OS and the network interfaces setup, this is not true. This change makes the test consider that both IPv4 or IPv6 sockets are valid Fixes #8096. Signed-off-by: Timothy J Fontaine <tjfontaine@gmail.com>	11 years ago
Julien Gilli	7da63a10ac	test: fix test-net-remote-address-port Do not use first socket in second socket's connect handler. Probably a copy/paste mistake. Reviewed-by: Trevor Norris <trev.norris@gmail.com>	11 years ago
Jackson Tian	e1ce8ba639	net: add remoteFamily for socket Signed-off-by: Fedor Indutny <fedor@indutny.com>	11 years ago
isaacs	695abba5ac	test: Fix many tests for streams2 net refactor	12 years ago
Ben Noordhuis	fd29448be0	test: add missing copyright headers	13 years ago
Bert Belder	e20d0c1cd0	net-uv: correctly set socket.remoteAddress and -port closes #1345	14 years ago
Ben Noordhuis	79f064f565	net: properly export remoteAddress to user land Fixes failing test: test/simple/test-net-remote-address-port.js	14 years ago
Ben Noordhuis	f52a8db280	test: fix logic error in test-net-remote-address-port.js The test intended to register an 'at exit' listener but called `process.exit()` instead.	14 years ago
Brian White	ac1da4b407	Add remoteAddress and remotePort for client TCP connections https://groups.google.com/d/topic/nodejs-dev/Asr87_YFSkg/discussion	14 years ago