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

Improve error message on websocket client close #392

Merged
merged 1 commit into from
Jan 3, 2025

Conversation

Ongy
Copy link
Contributor

@Ongy Ongy commented Jan 2, 2025

Currently the server side prints the error message every time the client sends the Close frame. Since the frame is sent on most connections, this leads to unneccary spam. I haven't tested the http2 variant, but from looking at the code, it follows the same pattern with a different ErrorKind.

With the lower priority log level, this can be filtered easily. The distinct messages also help with checking the logs by hand.

Currently the server side prints the error message every time the client sends the Close frame.
Since the frame is sent on most connections, this leads to unneccary spam.
I haven't tested the http2 variant, but from looking at the code, it follows the same pattern with a different ErrorKind.

With the lower priority log level, this can be filtered easily.
The distinct messages also help with checking the logs by hand.
@erebe
Copy link
Owner

erebe commented Jan 3, 2025

Thank you ;)

@erebe erebe merged commit 57788a6 into erebe:main Jan 3, 2025
13 checks passed
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

Successfully merging this pull request may close these issues.

2 participants