New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Duplicate Sec-WebSocket-Protocol headers in response #2135
Comments
Thanks for reporting. Apart from that, do you observe any mal-functioning on the client-side caused by this duplication? |
Chrome throws a console error about that behavior (duplicate headers) and websocket client dies. So it's kind of blocking issue really.
|
Ok, fair enough. Would you have time to send a PR for this? |
any workaround for this? |
Hi @jayachandrak, this is not currently planned as a high priority on our short-term schedule but if you can send a PR we'll gladly have a look and merge it. |
…r in response when a subprotocol is defined
…r in response when a subprotocol is defined
…r in response when a subprotocol is defined
…r in response when a subprotocol is defined
This issue still persists and the fix has not been implemented or rolled out. Why? This basically blocks web socket development in Chrome and even in iOS. |
Yes. This fix not backported to |
Potential bug with websockets response. I get 2x Sec-WebSocket-Protocol headers in response if I open websocket with a protocol parameter in JS like this
var socket = new WebSocket("ws://localhost:9000/ws", "some-arbitrary-text");
Lagom 1.5.1
Typical bidi streaming service signature:
def stream(): ServiceCall[Source[String, NotUsed], Source[String, NotUsed]]
The text was updated successfully, but these errors were encountered: