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
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.
The text was updated successfully, but these errors were encountered:
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.
The text was updated successfully, but these errors were encountered: