Skip to content
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

If connection closed by internal transport, callback not fired #1114

Open
Bolderaysky opened this issue Oct 31, 2023 · 0 comments
Open

If connection closed by internal transport, callback not fired #1114

Bolderaysky opened this issue Oct 31, 2023 · 0 comments

Comments

@Bolderaysky
Copy link

Version: 0.8.3-dev
Transport: external asio
If some connection problems causes internal transport to close connection, callback set in .set_close_handler isn't fired. I can see asio printing out errors about connection loss, but websocketpp doesn't do anything about that. I wanted to use open and close events for corresponding to connection resource management, but i can't really do it while close not fired in case of transport errors.

Most of the time, in such cases I see this error

[2023-10-30 11:11:42] [error] handle_read_frame error: websocketpp.transport:7 (End of File)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant