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
Client code might be interested in handling specific websocket handshake HTTP errors like 404, 403 etc differently. These currently just result in generic human-readable messages like raise Kontena::Websocket::ProtocolError, "Error during WebSocket handshake: Unexpected response code: 404", which are clumsy to deal with.
Looks like the Websocket::Driver::Client will set the http @status and @headers before failing the handshake and emitting the error.
The same error also gets emitted on things like Invalid HTTP response, though.
The text was updated successfully, but these errors were encountered:
Client code might be interested in handling specific websocket handshake HTTP errors like 404, 403 etc differently. These currently just result in generic human-readable messages like
raise Kontena::Websocket::ProtocolError, "Error during WebSocket handshake: Unexpected response code: 404"
, which are clumsy to deal with.Looks like the
Websocket::Driver::Client
will set the http@status
and@headers
before failing the handshake and emitting the error.The same error also gets emitted on things like
Invalid HTTP response
, though.The text was updated successfully, but these errors were encountered: