Skip to content

There is a bug in socket.io-client version 4.8.1. #5327

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
khadem-mh opened this issue Apr 9, 2025 · 1 comment
Open

There is a bug in socket.io-client version 4.8.1. #5327

khadem-mh opened this issue Apr 9, 2025 · 1 comment
Labels
to triage Waiting to be triaged by a member of the team

Comments

@khadem-mh
Copy link

When the connection between the client and server is established for the first time, everything works fine. However, as soon as the user goes offline and the socket.io-client attempts to reconnect between the client and server, there’s no issue up to this point. But the problem occurs when the user comes back online. In this case, an HTTP request is sent, but the middleware doesn’t execute, and the connection event is triggered directly. If there’s an authentication middleware, it won't be executed, causing the program to break. Both the server and client versions being used are 4.8.1. However, I didn’t encounter this issue with version 4.0.1, which I tested on the client side, and the program didn't break.

@khadem-mh khadem-mh added the to triage Waiting to be triaged by a member of the team label Apr 9, 2025
@wes337
Copy link

wes337 commented May 16, 2025

I think this is the same bug as #5197

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
to triage Waiting to be triaged by a member of the team
Projects
None yet
Development

No branches or pull requests

2 participants