Skip to content

DISCONNECT messages created in StompSubProtocolHandler do not contain user information [SPR-12215] #16829

@spring-projects-issues

Description

@spring-projects-issues

Rob Winch opened SPR-12215 and commented

This seems to be related to the fact that StompSubProtocolHandler.createDisconnectMessage does not set the user as handleMessageFromClient does.

Disconnect Message Headers

simpMessageType=DISCONNECT, 
stompCommand=DISCONNECT, 
simpSessionAttributes={httpSession.id=873A1B90ECB3370ECBC1F51E01DAB6E2}, simpSessionId=6

Connection Message Headers

simpMessageType=CONNECT, 
stompCommand=CONNECT, 
nativeHeaders={accept-version=[1.1,1.0], heart-beat=[10000,10000]},
simpSessionAttributes={httpSession.id=873A1B90ECB3370ECBC1F51E01DAB6E2}, 
simpUser= ...,
simpSessionId=6

Affects: 4.1 GA

Referenced from: commits 4af9851

Metadata

Metadata

Assignees

Labels

in: webIssues in web modules (web, webmvc, webflux, websocket)type: enhancementA general enhancement

Type

No type

Projects

No projects

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions