Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Issue #11398 - allow frames to be demanded in WebSocket onOpen #11402

Conversation

lachlan-roberts
Copy link
Contributor

closes #11398

An alternate to this fix would be succeeding the FrameHandler.onOpen callback before calling the openHandle in JettyWebSocketFrameHandler.

Signed-off-by: Lachlan Roberts <lachlan@webtide.com>
Signed-off-by: Lachlan Roberts <lachlan@webtide.com>
Signed-off-by: Lachlan Roberts <lachlan@webtide.com>
@lachlan-roberts lachlan-roberts self-assigned this Feb 21, 2024
Signed-off-by: Lachlan Roberts <lachlan@webtide.com>
gregw
gregw previously approved these changes Feb 22, 2024
Copy link
Contributor

@gregw gregw left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

A little niggle/suggestion, otherwise OK

Signed-off-by: Lachlan Roberts <lachlan@webtide.com>
@joakime joakime added the Bug For general bugs on Jetty side label Feb 23, 2024
@lachlan-roberts lachlan-roberts merged commit d3f19bb into jetty-12.0.x Feb 27, 2024
7 of 8 checks passed
@lachlan-roberts lachlan-roberts deleted the jetty-12.0.x-11398-WebSocket-CloseChannelException branch February 27, 2024 06:11
# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
Bug For general bugs on Jetty side
Projects
No open projects
Status: ✅ Done
Development

Successfully merging this pull request may close these issues.

WebSocket ClosedChannelException when demanding frames in onOpen
4 participants