Enable HTTP compression for REST client only #46414
Replies: 3 comments
-
/cc @cescoffier (rest-client), @geoand (rest-client) |
Beta Was this translation helpful? Give feedback.
0 replies
-
Your assessment is correct, but should absolutely provide more fine grained control over the setting. I am going to convert the discussion to an issue so we can address it. |
Beta Was this translation helpful? Give feedback.
0 replies
-
Done in #46415 (available since Quarkus 3.21) |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
I have a REST API that acts like a middleware between clients and another "external" REST API.
To send requests to the external API, I use a REST client. I want to enable HTTP compression in the REST client, but not in my REST API. Mostly because I have a nginx in front of my REST API that handles compression so it's handled outside of the Quarkus app.
Is this possible?
From what I saw in the documentation, to enable HTTP compression in REST client, I have to use
quarkus.http.enable-compression=true
.https://quarkus.io/guides/rest-client#receiving-compressed-messages
But this option will also enable global HTTP compression for my API: https://quarkus.io/guides/http-reference#http-compression
I might find some way to make what I want, but I'm wondering if there is a way to easily enable compression only for REST client.
Beta Was this translation helpful? Give feedback.
All reactions