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

fix #970 Separate HTTP and WebSocket compression configuration when on the server side. #980

Merged
merged 1 commit into from
Jan 31, 2020

Conversation

violetagg
Copy link
Member

Fix #970

@@ -97,7 +97,7 @@
.set(replaced.nettyRequest.headers());

if (channel().pipeline()
.get(NettyPipeline.CompressionHandler) != null) {
.get(NettyPipeline.CompressionHandler) != null || webSocketSpec.compress()) {

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Maybe better move webSocketSpec.compress() to first check condition, because CompressionHandler can present but webSocketSpec.compress() is disabled. WDYT ?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Done
Also the check with CompressionHandler will be removed in 1.0.x once I merge this change to master, but for 0.9.x we need to keep the current behaviour.

@amizurov
Copy link

LGTM, @rstoyanchev how we can adopt this configuration to SpringBoot org.springframework.boot.web.embedded.netty.NettyWebServer, should i create feature request ?

@rstoyanchev
Copy link
Contributor

@amizurov if you could please start with a request in https://github.com/spring-projects/spring-framework to add a property for this, both client and server side. Similar to the handlePing property I just added for 5.2.4.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants