Websocket client not connecting to the socket.io server

[hrishibawane]

I have a basic socket.io server (version 4.4.1) to which I am trying to connect with a C++ websocket client.
If I use ?EIO=3&transport=websocket as query parameters in the URL, the connection is successful and the io.on("connection") event is triggered on the server.
However, if I use ?EIO=4&transport=websocket, the connection does get successful but the io.on("connection") event is not triggered on server.

I have even tried from Postman client using Raw Websocket client too. It shows the same behaviours with EIO=3 and EIO=4.
I understand that socket.io has additional handling over raw websocket connection, but when connecting with EIO=3 in the URL, there
are no issues seen. I also understand that after v2, the breaking change was the reversal of Ping/Pong messages. However, that part comes later in the socket life cycle. This issue I am facing is concerning the point of connection at which different behaviours are seen with Engine.io versions.

Any pointers on what extra needs to be done on the client or server side to resolve this?

[hrishibawane]

So after debugging a lot I was able to figure this out.
The issue is that when using EIO v3 the server sends the CONNECT message packet. However, for EIO v4, the client has to send the CONNECT message packet.
CONNECT message packet is identified by text 40 where,
4 => engine.io packet type MESSAGE
0 => socket.io packet type CONNECT

This needs to be in the migration documentation along with the reversal of ping/pong messages.

[darrachequesne]

Hi! You can find more details about the Engine.IO & Socket.IO protocols there:

• https://github.com/socketio/engine.io-protocol
• https://github.com/socketio/socket.io-protocol

[Notadumdum]

@hrishibawane hey brother I have questions on this

[sergi]

I'm having this problem now. It's very confusing to me that allowEIO3: true doesn't prevent this. What's the point of that directive, if v2 clients can't connect to it anyway? Is there a way to prevent v4 to send the 40 on connect?

[Notadumdum]

Use a websocket client instead.. socket.io prevents you from successfully connecting. Thats what i did..

…

On Thu., Jan. 16, 2025, 4:40 a.m. Sergi Mansilla, ***@***.***> wrote: I'm having this problem now. It's very confusing to me that allowEIO3: true doesn't prevent this. What's the point of that directive, if v2 clients can't connect to it anyway? Is there a way to prevent v4 to send the 40 on connect? — Reply to this email directly, view it on GitHub <#4299 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AZCKOWU67YHXP57D4T646W32K55CBAVCNFSM6AAAAABVJFMOZKVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTCOBVGI4DAMI> . You are receiving this because you commented.Message ID: <socketio/socket. ***@***.***>