Bug: `connect` event will not fire on browser client about socket.io-client HOT 6 CLOSED

We can mark this issue as solved.

The implementation in the production server was incorrect. This only used the engine.io protocol sub-protocol. Then of course it is clear if the corresponding events are not thrown.

Sorry for the inconvenience

from socket.io-client.

Hi! Do you get a connect_error event instead?

socket.on('connect_error', (err) => {
  console.log('"connect_error" event was fired', err)
});

from socket.io-client.

1. i do not get an connect_error event
2. for testing I used a socket.io server with Node
3. i used a Jetty server for testing with the WebClient

Could it be that the connect event is only thrown when connecting to a socket io server?

from socket.io-client.

for testing I used a socket.io server with Node
i used a Jetty server for testing with the WebClient

Which server implementation are you using, the Node.js one?

If you enable the debug logs (by setting localStorage.debug = '*' in your console), do you get any useful information?

from socket.io-client.

The production server is the Jetty server, on which it does not work 100 per cent. The debugging does not produce any further output in the console.

It establishes the connection and also sends data:

I have to do some weird workarounds to make the connection work:

socket.io.on('open', () => {
  socket.onconnect();
});

socket.onAny((data) => {
  console.log('Here comes my data', data);
});

socket.on('message', (msg) => {
  console.log('Here comes no data', data);
});

from socket.io-client.

After the 40... message (which means "I want to enter the namespace named /statistics/websocket/stat1/"), the client should get a response from the server ("OK for namespace /statistics/websocket/stat1/"), which does not seem to be the case here.

It sounds like a bug. Could you please open an issue on the repository of the Jetty server?

from socket.io-client.