Skip to content
New issue

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

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

Already on GitHub? # to your account

Pass WebSocket closure code to Socket.IO Server on "transport close" reason #5234

Open
bryghtlabs-richard opened this issue Nov 21, 2024 · 0 comments
Labels
enhancement New feature or request

Comments

@bryghtlabs-richard
Copy link

Is your feature request related to a problem? Please describe.

We've been working through some connection stability issues with an embedded device with custom Socket.IO client, and I would like to know more information from our Socket.IO 4.7.5 service whenever a Socket.IO client connection is lost due to WebSocket "transport close".

Describe the solution you'd like

For the mainline Socket.IO client-API, the "disconnect" event has an additional "details" parameter that is quite useful. I would like a similar parameter for the server-API. In this "details" parameter, I'd like to be able to retrieve the WebSocket Status Code .

Describe alternatives you've considered
I've considered printing a backtrace each time, and trying to work out what happened from that, but it seems quite intrusive and generates a lot of logging.

@bryghtlabs-richard bryghtlabs-richard added the enhancement New feature or request label Nov 21, 2024
# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant