Skip to content

Conversation

@lachlan-roberts
Copy link
Contributor

Closes #12660

Expose the tag() and getTag() methods which are available on the org.eclipse.jetty.client.Request also on ClientUpgradeRequest and CoreClientUpgradeRequest so they can be used for WebSocket Upgrades.

Signed-off-by: Simone Bordet <[email protected]>
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.

Looks good on core, but should you not do the same change in the eeN versions of ClientUpgradeRequest?

@lachlan-roberts lachlan-roberts moved this to 👀 In review in Jetty 12.1.6 Dec 30, 2025
@lachlan-roberts
Copy link
Contributor Author

@sbordet we don't have specific EE versions of the Jetty client for EE10+, only websocket-core and jetty-core APIs.

We do for EE9/EE8, although I don't think it is necessary to add this to EE9/EE8.

@lachlan-roberts lachlan-roberts merged commit a732c28 into jetty-12.1.x Jan 6, 2026
9 checks passed
@github-project-automation github-project-automation bot moved this from 👀 In review to ✅ Done in Jetty 12.1.6 Jan 6, 2026
@lachlan-roberts lachlan-roberts deleted the fix/jetty-12.1.x/12660-ClientUpgradeRequest-tagging branch January 6, 2026 02:10
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

Status: ✅ Done

Development

Successfully merging this pull request may close these issues.

Tagging the ClientUpgradeRequest to be able to support per-reqiest client ssl auth

3 participants