-
Notifications
You must be signed in to change notification settings - Fork 411
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
WebSocketConfig.withForwardCloseFrames does not forward Close frames #2375
Comments
/bounty $75 |
|
/attempt #2375 Options |
val run: ZIO[Scope, Throwable, Any] = Try that |
💡 @webberaj81 submitted a pull request that claims the bounty. You can visit your org dashboard to reward. |
…rward Close frames fix typos, clarify descriptor add WebSocketConfig unit test for forwardCloseFrames
/attempt #2375 Options |
Note: The user @webberaj81 is already attempting to complete issue #2375 and claim the bounty. If you attempt to complete the same issue, there is a chance that @webberaj81 will complete the issue first, and be awarded the bounty. We recommend discussing with @webberaj81 and potentially collaborating on the same solution versus creating an alternate solution. |
@an0nym3sh: Reminder that in 7 days the bounty will become up for grabs, so please submit a pull request before then 🙏 |
… frames #2375 (#2395) * fix bug #2375 - WebSocketConfig.withForwardCloseFrames does not forward Close frames fix typos, clarify descriptor add WebSocketConfig unit test for forwardCloseFrames * * scalafmtAll * * scalafmtAll * * typo fix * squash! * typo fix * scalafmtAll * squash! squash! * typo fix * remove unused layer * squash! squash! squash! * typo fix * run sFix
🎉🎈 @webberaj81 has been awarded $75! 🎈🎊 |
Describe the bug
When creating a WebSocketConfig with
withForwardCloseFrames(true)
, Close frames are not forwarded.To Reproduce
Steps to reproduce the behaviour:
Read(WebSocketFrame.Close)
to some observable behavior, e.g.,Console.printLine
Read(WebSocketFrame.Close)
eventExpected behaviour
Methods have functionality consistent with their naming
Additional context
WebSocketConfig.withForwardCloseFrames(false)
does forward the Close frames to the client, which is contradictory to it's name, and to the behavior of its sibling method,WebSocketConfig.withForwardPongFrames
, which requirestrue
to be made visible to the Client/ServerTo put this another (more readable) way, this is what the WebSocketClient from the example code would need to be to see Close frames and Pong frames, both of which are not available by default:
The text was updated successfully, but these errors were encountered: