-
Notifications
You must be signed in to change notification settings - Fork 2.8k
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
Allow more fine-grained control of compression setting for REST Client #46417
Conversation
geoand
commented
Feb 21, 2025
•
edited
Loading
edited
- Closes: Enable HTTP compression for REST client only #46415
🙈 The PR is closed and the preview is expired. |
Status for workflow
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Any reason why the compression is handled using an interceptor and not the underlying client?
@@ -1755,9 +1755,22 @@ The code uses the following pieces: | |||
As previously mentioned, the body parameter needs to be properly crafted by the application code to conform to the service's requirements. | |||
|
|||
=== Receiving compressed messages | |||
REST Client also supports receiving compressed messages using GZIP. You can enable the HTTP compression support by adding the property `quarkus.http.enable-compression=true`. | |||
REST Client also supports receiving compressed messages using GZIP and can be enabled via configuration. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm surprised it does not handle the other compression protocols like Brotli.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Also something to check as a follow up
@@ -278,7 +278,7 @@ public ClientImpl build() { | |||
} | |||
} | |||
|
|||
if (enableCompression) { | |||
if (Boolean.TRUE.equals(enableCompression)) { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ah that's why. It is done using an interceptor.
Any reason for this?
That's a good question, I didn't do the initial implementation, so I'll have to check that as a follow-up |
I'll be looking at #46496 this week |