You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm using Firefox (108.0, MacOS 13.1).
When I run this project, the browser debugger shows there's some 500 responses from the server.
I added this code to the index.js, and the server console logs:
io.engine.on("connection_error",(err)=>{// console.log(err.req); // the request objectconsole.log(err.code);// the error code, for example 1console.log(err.message);// the error message, for example "Session ID unknown"console.log(err.context);// some additional error context});
I guess the problem is: the websocket connection was established successfully, but the polling connection failed.
So I tried to add a parameter to allow only polling:
Then, the connection never establishes successfully. The browser sends requests and gets 500 responses infinitely. The server also gets "Session ID unknown" infinitely.
Looks like a new connection starts to establish when the previous connection hasn't finished establishing.
I've tried the latest version (4.5.4) of "socket.io" and "socket.io-client", the behavior is the same.
And I found the polling connection can be successfully established in the latest version of Chrome, but failed in Edge as in Firefox.
Activity
hatsuroku commentedon Dec 16, 2022
Except the code showed above, the rest of the code is exactly the same as the repositories.
hatsuroku commentedon Dec 16, 2022
Edge (108.0.1462.54, windows 11 22H2)
hatsuroku commentedon Dec 16, 2022
Chrome (108.0.5359.125, windows 11 22H2)

The connection is established successfully.
darrachequesne commentedon Sep 7, 2023
@hatsuroku were you able to find the cause of the issue?