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

Issue #5018 - add WebSocketClient UpgradeRequest timeout to jetty 10 #5031

Merged

Conversation

lachlan-roberts
Copy link
Contributor

Changes for Jetty-10 based off PR #5024 for issue #5018.

I have changed the signature for WebSocketClient.connect() back to what it was in jetty 9.4.x, it is now taking a ClientUpgradeRequest and not the api UpgradeRequest. This is an API change so not sure if that is still okay now the beta release is out.

I don't think we want the timeout on the org.eclipse.jetty.websocket.api.UpgradeRequest as it is only usable for the clients upgrade request anyway.

Signed-off-by: Lachlan Roberts <lachlan@webtide.com>
@gregw gregw linked an issue Jul 8, 2020 that may be closed by this pull request
@gregw
Copy link
Contributor

gregw commented Jul 8, 2020

This failed CI? But no problems changing API like this in a Beta.... but last chance as we are going final real soon now!

Signed-off-by: Lachlan Roberts <lachlan@webtide.com>
…5018-WebSocketClientRequestTimeout

Signed-off-by: Lachlan Roberts <lachlan@webtide.com>
Signed-off-by: Lachlan Roberts <lachlan@webtide.com>
@lachlan-roberts lachlan-roberts merged commit fc473f3 into jetty-10.0.x Jul 15, 2020
@lachlan-roberts lachlan-roberts deleted the jetty-10.0.x-5018-WebSocketClientRequestTimeout branch July 15, 2020 23:19
joakime added a commit that referenced this pull request Aug 21, 2020
Signed-off-by: Joakim Erdfelt <joakim.erdfelt@gmail.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

WebSocketClient connect / upgrade timeout not configurable
4 participants