Reported by Kadir Pekel <email@example.com>
Made this test in response to this thread: http://groups.google.com/group/nodejs/browse_thread/thread/f82835007a277de2/ But Node appears to be working correctly.
onend and ondata was cleaning on parser end
rnewson found a good bug in keep-alive. we were only using the request headers we send to enable/disable keep-alive but when the server sends Connection: close we need to close down the connection regardless. I wrote up a patch the Robert verified makes all his test client code work now and I also added a new unittest for it.
Simplify and correct test. Fix by Fedor Indutny.
- Add test case for pumping from unreadable stream. - Document the sys.pump error handling behavior
And fix missing var! It would be good to get this script running at the end of every test, so we know that modules aren't leaking either - but it will require a lot modification of the tests so that they themselves aren't leaking globals.
…ldren. Found by Cliffano Subagio http://groups.google.com/group/nodejs/browse_thread/thread/f46f093938265ac0/387e14da08c7dd7b?
Expose the SHA1 digest of the certificate as the fingerprint attribute in the object returned by getPeerCertificate()
Add a setUp and tearDown function to the test case class, and use it to create and remove the test/tmp directory for each test. TODO: amend other tests.
Previously we would only call it before going into select(). This is needed to fix test/simple/test-next-tick-ordering2.js.
Using "global" to push data to require()d modules not supported under NODE_MODULE_CONTEXTS=1.
nextTick should fire before setTimeout in this test, but it doesn't.
Change process._tickCallback so that if a callback throws an error but there are other callbacks after it, we indicate that process._tickCallback needs to be ran again. Currently, if a callback in process._tickCallback throws an error, and that error is caught by an uncaughtException handler and process.nextTick is never called again, then any other callbacks already added to the nextTickQueue won't be called again. Updated the next-tick-errors test to catch this scenario.
Note that "//" is still a special indicator for the hostname, and this does not change the parsing of mailto: and other "slashless" url schemes. It does however remove some oddness in url.parse(req.url) which is the most common use-case for the url.parse function.
Test running already has a timeout mechanism.