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
{{ message }}
This repository has been archived by the owner on Dec 7, 2018. It is now read-only.
If the incoming ws request before upgrade had
Sec-WebSocket-Protocol
header, the reply should include that header as well.With Websocket::Driver you can handle that by using the
protocols
option: https://github.com/faye/websocket-driver-ruby#driver-apiWith that set, the driver will automatically negotiate the protocol. In reel, we are unable to set this option, due to how the driver is initialized: https://github.com/celluloid/reel/blob/master/lib/reel/websocket.rb#L20
This causes reel to never send the subprotocol header.
In result reel is unusable when the browser sends in the protocol value - the websocket will be closed by the browser with following error:
The text was updated successfully, but these errors were encountered: