Zuul not returning gzip responses correctly
See original GitHub issueWhen I hit one of my services that returns gzipped data but Zuul always return plain-text responses. At first I thought it was ignoring the Accept-Encoding header but it seems to be forwarding it correctly.
They’re both running on Spring Cloud: Camden.RELEASE
The configuration for the service includes:
compression:
enabled: true
mime-types: application/json,application/xml,text/html,text/xml,text/plain,application/json;charset=UTF-8
min-response-size: 64
Issue Analytics
- State:
- Created 6 years ago
- Comments:27 (9 by maintainers)
Top Results From Across the Web
Returning a GZipped response using Spring Cloud Gateway ...
I'm using Spring Cloud Gateway to forward requests to a back-end service. Since some of our back-end services send out their results gzipped, ......
Read more >spring-cloud/spring-cloud - Gitter
anyone know how to tell zuul not to uncompress gzip requests? i debugged the code ... it work everything fine and I get...
Read more >Configuration — Zuul documentation
It receives events from any connections to remote systems which have been configured, enqueues items into pipelines, distributes jobs to executors, and reports ......
Read more >Eureka Server - Spring Cloud Netflix
The Spring Cloud DiscoveryClient will always return a URI starting with ... You may consider enabling the request or response GZIP compression for...
Read more >Open Sourcing Zuul 2 - Netflix TechBlog
The outbound filters run after a response has been returned and can be used for things like gzipping, metrics, or adding/removing custom ...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
@ryanjbaxter i have upgraded to Dalston.SR5 and everything looks good. But we have issues in our AWS environment and we are not seeing the final response in the client side. Thank you for the needed help.
We can look at not adding the header if it is already present. Not sure why it is forcefully added. Please open another issue.