Skip to content
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

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

Closed
spring-projects-issues opened this issue Sep 17, 2014 · 0 comments
Assignees
Labels
in: web Issues in web modules (web, webmvc, webflux, websocket) type: enhancement A general enhancement
Milestone

Comments

@spring-projects-issues
Copy link
Collaborator

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

@spring-projects-issues spring-projects-issues added type: enhancement A general enhancement in: web Issues in web modules (web, webmvc, webflux, websocket) labels Jan 11, 2019
@spring-projects-issues spring-projects-issues added this to the 4.1.1 milestone Jan 11, 2019
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: enhancement A general enhancement
Projects
None yet
Development

No branches or pull requests

2 participants