Propagate exceptions to the client

[itayAmza]

Hi,
Related to this StackOverflow post, I'm looking for best practices to communicate exceptions to the client.
I have 3 key point where I want to notify client about errors:

1. Connection rejected reason
2. Authentication middleware exceptions
3. In-session data processing

as per the third one, I'm currently using try statement to catch exceptions and send them over "error type" socket.
Not sure if this is best practice but I figured that way I can prevent the connection from being closed.

Anyway I'll be happy for any guide or an example, or even a shot explanation about best practices for error handling. and if there is a way to propagate exceptions as http response errors instead of getting 1011 - There was a bad response from the server all the time.

The full post with code examples in here

[bishaldahal4777]

Hey! 👋
For connection and auth errors, it’s better to raise DenyConnection() instead of letting exceptions crash the socket.
Inside middleware, catch exceptions and close cleanly — don’t just let them bubble up.
For in-session errors, what you’re doing (try/except and sending an "error" message) is actually a good approach. That way, the connection stays alive and you can send proper error types to the client.
WebSockets can’t send real HTTP error codes after upgrade, so just use JSON error messages like
{"type": "error", "message": "something went wrong"}
That’s the usual “best practice” way to handle it. 👍