Skip to content
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

WebSocketUpgradeHandler should not require ContextHandler #10768

Merged
merged 6 commits into from
Nov 20, 2023

Conversation

lachlan-roberts
Copy link
Contributor

WebSocketUpgradeHandler should not be required to be wrapped inside a ContextHandler

@sbordet
Copy link
Contributor

sbordet commented Oct 23, 2023

@lachlan-roberts can you explain why you need this? I'm not against it, just curious about why.
Please add the project this PR belongs to (and an issue if any).

@lachlan-roberts
Copy link
Contributor Author

I don't specifically need this and I did not create an issue for it. I just saw these tests and didn't think the WebSocketUpgradeHandler should be forced to be under a ContextHandler.

We don't require a ContextHandler for the websocket-core upgrade handler.

Signed-off-by: Lachlan Roberts <[email protected]>
… the WebSocketUpgradeHandler with only the Server, to allow dynamic configuration of WebSocket endpoints.

Signed-off-by: Simone Bordet <[email protected]>
sbordet
sbordet previously approved these changes Nov 20, 2023
Copy link
Contributor

@sbordet sbordet left a comment

Choose a reason for hiding this comment

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

@lachlan-roberts I have updated WebSocketUpgradeHandler to expose the ServerWebSocketContainer as attribute also when created with only the Server.
LGTM now.

@sbordet sbordet merged commit b8ece59 into jetty-12.0.x Nov 20, 2023
5 checks passed
@sbordet sbordet deleted the jetty-12.0.x-WebSocketUpgradeHandler branch November 20, 2023 18:30
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
No open projects
Status: ✅ Done
Development

Successfully merging this pull request may close these issues.

2 participants