socket.io from v1.0.x return error on handshake about elephant.io HOT 16 CLOSED

It's working on my stage server, not on my local server

from elephant.io.

I get same error with socket.io 1.0.4.

from elephant.io.

Handshake is different from 1.0.0. I had an old version in local.

from elephant.io.

Same issue here for 1.0.4, any workaround ?

from elephant.io.

I also get the same issue

from elephant.io.

Same issue here. Would be great to see an update soon

from elephant.io.

Hi there,

Thanks for using elephant.io and for opening this issue. It seems that socket.io 1.x changed a bit its payload and that elephant is currently running only for 0.x socket.io versions.

We planned to take time to support it properly during july. Please be patient or submit a PR to help us before we have time to have a closer look to that.

Thanks a lot

from elephant.io.

This may help you, I posted it to stackoverflow in response to someone else with a similar issue.
http://stackoverflow.com/questions/23946683/socket-io-bad-request-with-response-code0-messagetransport-unknown

from elephant.io.

Here is a quick fix in Client.php line 331:

    $sess = json_decode(substr($res,5));
    $this->session['sid'] = $sess -> sid;
    $this->session['heartbeat_timeout'] = $sess -> pingInterval;
    $this->session['connection_timeout'] = $sess -> pingTimeout;
    $this->session['supported_transports'] = array_flip($sess -> upgrades);

from elephant.io.

Thanks for your fix.

It removes the error, since Socketio1.x doesn't allow websocket connections first. You have to connect through a polling connection, and then upgrade to websocket, if supported.

However, they changed many things in the way they handle their communications, by switching to Engineio. Even if it removes the error, you won't be able to send any message. The current Elephantio implementation is meant to work with Socketio 0.9.x, and needs a huge refactoring to work with Socketio 1.x.

We tried working on it but found no "quick fix", and planned refactoring the lib within a few weeks

from elephant.io.

I made a pulling request with a quick fix. Tell me if it's good.

from elephant.io.

Hey @guillaumepotier, what about the support planed in July ? :)

from elephant.io.

Ahah, nice reminder @sroze ;)

Like every project planning and management, we experienced some delays :) But @Taluu is starting 3.0 refacto / branch right now, and have exactly 5 working days to achieve that (after it would be me during my holidays :p)

Thanks to @lalmat I think the task will be easier for us ;)

Best

from elephant.io.

Which way do you want to manage its implementation ? By using the Client's protocol parameter ? Create an 0.x branch for the current code and 1.0 support only on the master branch ?

@guillaumepotier 5 working days seams great for the community ! :)

from elephant.io.

See my comment on @lalmat's pull request : #53 (comment)

The idea would be to have several "engines" which decide how to speak with the target (Socket.io 0.x, Socket.io 1.x, ... etc).

from elephant.io.

Closing, as Elephant 3 now supports Socket.io 3.0. A "true" stable release should be available during the month.

from elephant.io.