Compatibility with v0.10

[peter-henning]

Noticed after upgrading to 0.10 I am getting connection timeouts anytime I try to connect to a database. Have you tested with the new version of Node and see any similar issues?

[pekim]

All of the integration test (except for one related to secure connections) pass when I run them.

[peter-henning]

Thanks for the quick response. We are using secure connections. Would that explain why we're seeing a timeout?

[pekim]

Yes, it would.

I noticing the problem with 0.9.x, and started investigating (https://groups.google.com/forum/#!searchin/nodejs/%22once$20the$20response$20has$20been$20received%22/nodejs/vc-yPrc3lsU/QnQpH84_sTQJ). As far as I can tell, 0.9.x switched to a later version of openssl, which has different default ciphers. But I've not had time to dig further.

You may be able to work around this by forcing use of RC4-MD5 (instead of the default DES-CBC3-SHA). This entails specifiying options.cryptoCredentialsDetails when creating the connection.

See:

• http://pekim.github.com/tedious/api-connection.html#function_newConnection .
• http://nodejs.org/docs/latest/api/tls.html#tls_tls_createsecurepair_credentials_isserver_requestcert_rejectunauthorized
• http://nodejs.org/docs/latest/api/crypto.html#crypto_crypto_createcredentials_details

So something like this (untested).

    options.cryptoCredentialsDetails = crypto.createCredentials({ciphers: 'RC4-MD5'})

[pekim]

The proposed workaround doesn't seem to work. I'm digging deeper in to node's tls and net modules.

[pekim]

It looks like it stops working entirely (even with RC4-MD5) with nodejs/node-v0.x-archive@d59beb9 . This is when the tls module was changed to use streams2.

This change affected a lot of lines. I guess that it's time that I get to grips with both the new stream api and the guts of the tls module.

[pekim]

It seems, if I'm understanding the tls module docs correctly, that node v0.10.x is not initiating the tls handshake.
I've raised nodejs/node-v0.x-archive#5140.