Document how websocket server implementations should be configured by users to limit message size [SPR-11023]

[spring-projects-issues]

Brian Clozel opened SPR-11023 and commented

---

Affects: 4.0 RC1

Issue Links:

• Validate message size limits in StompProtocolHandler [SPR-10892] #15520 Validate message size limits in StompProtocolHandler

[spring-projects-issues]

Brian Clozel commented

Documentation task

[spring-projects-issues]

Brian Clozel commented

Tomcat:
The WebSocketContainer exposes APIs to configure timeouts and maximum buffer sizes.

Jetty:
One can configure a WebSocketPolicy and set buffer sizes and timeouts as well (see Example in jetty codebase).

Glassfish:
Glassfish also implements the WebSocketContainer interface, see TyrusServerContainer.

Note: when enforced, those limits may close connections without sending high level protocol messages. When using STOMP, a frame/message longer than enforced limits won't send a STOMP error message (see #15520)