Skip to content

Drop server-specific WebSocket RequestUpgradeStrategy implementations (except Jetty) #33744

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

Closed
jhoeller opened this issue Oct 18, 2024 · 0 comments
Assignees
Labels
in: web Issues in web modules (web, webmvc, webflux, websocket) type: task A general task
Milestone

Comments

@jhoeller
Copy link
Contributor

Our server-specific WebSocket RequestUpgradeStrategy implementations are effectively legacy already when running on Jakarta WebSocket 2.1 (Jakarta EE 10). As of Spring Framework 7.0, they can be dropped completely due to the Jakarta EE 11 baseline.

@jhoeller jhoeller added in: web Issues in web modules (web, webmvc, webflux, websocket) type: task A general task labels Oct 18, 2024
@jhoeller jhoeller added this to the 7.0.x milestone Oct 18, 2024
@jhoeller jhoeller modified the milestones: 7.0.x, 7.0.0-M1 Nov 19, 2024
@jhoeller jhoeller self-assigned this Nov 19, 2024
@jhoeller jhoeller changed the title Drop server-specific WebSocket RequestUpgradeStrategy implementations Drop server-specific WebSocket RequestUpgradeStrategy implementations (except Jetty) Dec 3, 2024
jhoeller added a commit that referenced this issue Dec 4, 2024
StandardWebSocketUpgradeStrategy is the common replacement on Tomcat.

See gh-33744
bclozel added a commit that referenced this issue Dec 8, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
in: web Issues in web modules (web, webmvc, webflux, websocket) type: task A general task
Projects
None yet
Development

No branches or pull requests

1 participant