Skip to content

Commit 3edb256

Browse files
committed
Update websocket reference docs
See gh-33744
1 parent 2015a93 commit 3edb256

File tree

1 file changed

+1
-4
lines changed
  • framework-docs/modules/ROOT/pages/web/websocket

1 file changed

+1
-4
lines changed

framework-docs/modules/ROOT/pages/web/websocket/server.adoc

+1-4
Original file line numberDiff line numberDiff line change
@@ -85,10 +85,7 @@ for all HTTP processing -- including WebSocket handshake and all other HTTP
8585
requests -- such as Spring MVC's `DispatcherServlet`.
8686

8787
This is a significant limitation of JSR-356 that Spring's WebSocket support addresses with
88-
server-specific `RequestUpgradeStrategy` implementations even when running in a JSR-356 runtime.
89-
Such strategies currently exist for Tomcat, Jetty, GlassFish, WebLogic, WebSphere, and Undertow
90-
(and WildFly). As of Jakarta WebSocket 2.1, a standard request upgrade strategy is available
91-
which Spring chooses on Jakarta EE 10 based web containers such as Tomcat 10.1 and Jetty 12.
88+
a standard `RequestUpgradeStrategy` implementation when running in a WebSocket API 2.1+ runtime.
9289

9390
A secondary consideration is that Servlet containers with JSR-356 support are expected
9491
to perform a `ServletContainerInitializer` (SCI) scan that can slow down application

0 commit comments

Comments
 (0)