Propagate max frame length to WebSocket session by aavoronin93 · Pull Request #36370 · spring-projects/spring-framework
This change ensures that maxFramePayloadLength from WebsocketClientSpec is passed to ReactorNettyWebSocketSession. Previously, the session used the default 64KB limit regardless of client configuration, causing TooLongFrameException when receiving larger frames from servers like Tomcat or Jetty. Closes spring-projectsgh-36369 Signed-off-by: Artem Voronin <artem.voronin.dev@gmail.com>
rstoyanchev pushed a commit that referenced this pull request
Mar 5, 2026This change ensures that maxFramePayloadLength from WebsocketClientSpec is passed to ReactorNettyWebSocketSession. Previously, the session used the default 64KB limit regardless of client configuration, causing TooLongFrameException when receiving larger frames from servers like Tomcat or Jetty. See gh-36370 Signed-off-by: Artem Voronin <artem.voronin.dev@gmail.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters. Learn more about bidirectional Unicode characters