-
Notifications
You must be signed in to change notification settings - Fork 109
Conversation
This will fail badly on io.js/0.12 because |
Is there a way to use |
Doubt it. The v0.10.x HTTPS has a private I added a version check which fixes the problem at hand, but it didn't pass tests as |
I tried using this code branch (with
Whenever I add a hacky tweak to force the protocol: sudothinker@fa6efe7. I now get:
Not too sure why that second comes in, still investigating. I'm using node 0.12.1, replay 2.0.4 and zombie 3.1.0 |
FYI each protocol has a default port, but the port number doesn't dictate the protocol, so the URL So my guess is this code is trying to make an HTTP request, there's a lot of prep work that happens in |
Yeh I know that the port doesn't define the protocol, i just added that in so I could try forcing the https protocol. The resulting options which cause the timeout to
|
In 0.12/io.js the only thing you need to get HTTPS working is to make sure the Agent is HTTPS, which clearly is in your example. That's the only material difference between HTTP and HTTPS requests, see: https://github.com/joyent/node/blob/master/lib/https.js#L131 0.10 always required a bit more code to setup HTTPS requests: https://github.com/joyent/node/blob/v0.10.36-release/lib/https.js#L95-L124 |
Right, I even tried forcing the agent too: I can keep digging, it doesn't even seem to be running that long before it timeouts and I have zombie |
Just pushed this to master, SSL tests now happening, works well on io.js. |
Still no luck on node 0.12.1. I actually just tried it on io.js 1.6.2 and got the same problems. (either wrong protocol, or a timeout if you force the protocol). By default it looks like the options being passed to ClientRequest have |
Currently test suite passed on 0.10, 0.12 and io.js: https://travis-ci.org/assaf/node-replay (it was passing before, apparently by not running any of the code we're talking about) I have, however, no idea how/why the code works with 0.10. |
@sudothinker Maybe this is fixed by #62? |
Re-enables SSL tests - fixing at least #46