-
-
Notifications
You must be signed in to change notification settings - Fork 4.1k
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
Enabling Compression to Websocket on Netty #10863
Comments
Hey @TheAntimist did you manage to get it to work? |
Let's add this to the 2.9 release |
@TheAntimist Sure 😉 I am happy to review. |
@TheAntimist Will you work on this? |
@mkurz I started work on it, but got covid. Just getting recovered and starting work on this again soon. |
@TheAntimist Oh, I am sorry, hope you get better soon! I didn't want to push you, just asking if there is still interest. Take your time. |
@mkurz No worries, I intended on getting it done earlier. I will try to finish this within the upcoming 2-3 weeks once I get recovered. |
@mkurz Just to let you know I've started working on this again last week. Been testing it and checking a few things, hopefully I'll get it completed soon. |
Play Version
2.8.8
API
Java
Operating System
Windows and Linux
JDK
Actual Behavior
I am currently implementing a websocket server in Play. As part of doing that I noted that the server does not support the
permessage-deflate
Websocket Extension.Netty had added this as part of their 4.1 release . An example of a server implementation is here .
Possible Solution
I went over the codebase, and found that using the
ChannelPipeline
object during the handshake here, HttpStreamsServerHandler.java#L187 to add theWebSocketServerCompressionHandler
could work.Although, I cannot be certain if this would work or be the right way to achieve it, I could surely raise a PR, if someone pointed me in the right direction.
EDIT: I just checked that this was a duplicate of #4186 . But would like to atleast get a response on how to move forward before closing this issue.
The text was updated successfully, but these errors were encountered: