-
Notifications
You must be signed in to change notification settings - Fork 38.3k
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
Websocket extensions not working #26449
Comments
How does it break? Does it not find the installed extensions or something in the equals() of the wrapper? |
@rstoyanchev it finds the installed extension but it wraps it in a StandardToWebSocketExtensionAdapter, which makes the filterRequestedExtensions method not include it in the final list of extensions to apply to the request. I am thinking perhaps it should not be wrapped or the filterRequestedExtensions could be changed to filter by name and not Collection.contains(). |
Okay so |
I'll add a fix. A workaround could be to override |
@piotrblasiak I've committed a fix if you'd like to check it with a 5.3.4-SNAPSHOT in your codebase. |
@rstoyanchev I can confirm it has been fixed and it is now working as expected. Thank you! |
Great, thanks for testing it! I will now backport it to 5.2.x. |
Affects: \5.3.3
In spring, one can add an undertow websocket extension by:
But that extension does not work when processing requests. I have found that spring wraps extensions in
org.springframework.web.socket.server.standard.AbstractStandardUpgradeStrategy.getInstalledExtensions(...)
which breaks the extension matching in
org.springframework.web.socket.server.support.filterRequestedExtensions(...)
I have been unable to find a workaround for this, and I am not sure what an appropriate fix would be.
The text was updated successfully, but these errors were encountered: