-
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
Enable HTTP compression for REST client only #46415
Comments
/cc @cescoffier (rest-client) |
@jdussouillez can you try #46417 please? |
I tried but unfortunately I need more time to figure out how to use your branch into my project. I cloned your repo, switched your branch, run
When explicitly adding I'll find a solution and try ASAP |
FWIW, when I build Quarkus locally I use:
Then I use: <dependency>
<groupId>io.quarkus</groupId>
<artifactId>quarkus-bom</artifactId>
<version>999-SNAPSHOT</version>
<type>pom</type>
<scope>import</scope>
</dependency> as the BOM in any test application |
It's not my day I think.
|
What is the output of I have:
|
Same. I'm using SDKMan and switched to 17 (my apps are 21) to build Quarkus
|
I am out of ideas unfortunately |
New week, perhaps any luck on a new attempt to build this? |
Same as last week unfortunately. I checked and Quarkus 999-SNAPSHOT (built from your branch) is well installed in my I'm thinking about adding a temporary module in the Quarkus project. This module will contain a endpoint calling a REST client to test the new options you added. So I don't use "external" dependencies installed on my machine but the project modules themselves. |
I rebased the PR onto |
I was hoping, but same issues. Quarkus installation works fine, but I have a lot of errors when trying to use it. I created a small repo to use HTTP compression on REST client here: https://github.com/jdussouillez/quarkus-rest-client-compression But I can't build/start it using my local Quarkus. |
In your sample, you need to use |
It tried it and it works for me |
Yes I know, I tried some stuff. One of my coworker could build it correctly so we'll stop investigating on my machine. I'll make him test it. I'll give some feedback very soon. |
👍🏽 |
Allow more fine-grained control of compression setting for REST Client
I tested it using https://github.com/jdussouillez/quarkus-rest-client-compression I tested different configuration by switching on and off Thanks for your help and the quick feature development! |
Great, thanks for checking! |
Discussed in #46414
Originally posted by jdussouillez February 21, 2025
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.
The text was updated successfully, but these errors were encountered: