Status of ssl connect in current version about elephant.io HOT 7 CLOSED

The issue is in handshake. Getting a ServerConnectionFailureException. I have the ssl option for verify_peer set to false since elephant.io is connecting inside my server farm. I don't really need ssl for elephant.io, but it seems easer than having my socket.io server use both https and http together. Line 141 of Version1X.php doesn't seem to take into account my verify_peer = false option setting. When I get home, I'll try setting that and see if it makes any difference.

from elephant.io.

The difference with the 2.0 is that it is not using curl (or sockets) anymore to do the handshake, just a simple file_get_contents. But yeah, maybe there is something I could have missed.

If you find it, feel free to make a PR or keep us updated, and we'll check as soon as we'll have some time !

from elephant.io.

Since I actually don't NEED SSL for the back end php servers to connect to, I created a new http listener on my socket.io server and split client and server functions out. Clients still connect via SSL, and elephant.io connects without. Works fine. Solves the problem. So, for me, this is no longer an issue.
It actually adds some extra security because it removes the ability for any clients to send messages that should really only be initiated by the php servers. And clients cannot connect to the new server port due to the firewall. Probably should have been done anyway.

from elephant.io.

Got it, but I'm still leaving this issue open to put a reminder to think about it. :)

from elephant.io.

I'm using https without any problems...

from elephant.io.

Should be fixed by #103 (which still needs a full review and manual merging at the time this message is written)

from elephant.io.

@eprincen2 could You share You nodeJS code? This part exactly: I created a new http listener on my socket.io server and split client and server functions out. Clients still connect via SSL, and elephant.io connects without.

from elephant.io.