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.

Sign up for GitHub

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

Jump to bottom

Not possible to use custom connect headers in WebSocketHttpHeadersCallback #10

Open
lukasraska opened this issue Dec 28, 2017 · 1 comment
Open

Not possible to use custom connect headers in WebSocketHttpHeadersCallback #10

lukasraska opened this issue Dec 28, 2017 · 1 comment

Comments

@lukasraska
Copy link

Currently it's not possible to utilize any custom headers sent via STOMP connect command (for example custom authentication data). This is due to the fact that connectToProxiedTarget doesn't accept WebSocketMessageAccessor as other command methods do.
@lukasraska lukasraska mentioned this issue Dec 28, 2017
Open
@lukasraska
Copy link
Author

PR #11 solves the issue

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@lukasraska