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
I'm currently a bit unhappy with the error handling in the messages.
The websocket connect message for example... any error or exception happening in there will keep the connection open and the client will be able to continue sending messages.
It should be possible to drop the connection attempt by raising permission denied for example or it should fail with a error 500 on other exceptions.
Bastian
The text was updated successfully, but these errors were encountered:
I guess that would be a solution that would not require any changes.
I would prefer a solution that would directly work in the request where the websocket ist created (to fail that with forbidden for example) but I guess thats not easy to do.
I'm currently a bit unhappy with the error handling in the messages.
The websocket connect message for example... any error or exception happening in there will keep the connection open and the client will be able to continue sending messages.
It should be possible to drop the connection attempt by raising permission denied for example or it should fail with a error 500 on other exceptions.
Bastian
The text was updated successfully, but these errors were encountered: