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
When an error happens during upgrade of websocket, there's no way to process such error in a custom way.
What did you expect?
#1975 added possibility to specify handler func for errors, but it gets called only for errors happening at a later stage. It would be nice to get it called during upgrade as well e.g. when Upgrader calls CheckOrigin and origins don't match or when the client hasn't specified correct Sec-Websocket-Version etc
What happened?
When an error happens during upgrade of websocket, there's no way to process such error in a custom way.
What did you expect?
#1975 added possibility to specify handler func for errors, but it gets called only for errors happening at a later stage. It would be nice to get it called during upgrade as well e.g. when Upgrader calls CheckOrigin and origins don't match or when the client hasn't specified correct Sec-Websocket-Version etc
versions
github.com/99designs/[email protected]
go1.19.1 darwin/amd64
The text was updated successfully, but these errors were encountered: