tokers commented on pull request #4956: URL: https://github.com/apache/apisix/pull/4956#issuecomment-912169821
> > according to this document: https://github.com/Netflix/eureka/wiki/Example-Custom-ReadOnly-client, is it possible to specify Accept-Encoding in the header to control this? > > It seems like this PR is unnecessary, and my confusion is resolved mentioned on #4929 when I run eureka server via docker, also can specify "Accept-Encoding" of header to get compressed or uncompressed response. could I close this PR and issues ? And I will try to find out why got compressed response when start eureka server within Tomcat I have ever met some strange situations when I deploy an Eureka service, it doesn't respect the `Accpet-Encoding` header, compressed data is sent all the time. And, I want to know the handle about the `Accept-Encoding` in the current APISIX implementation. We may still have to decode the compressed data. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
