REST endpoint returning "content-encoding: gzip" header even when not encoded

[soaresGITHUB]

Describe the bug

As of at least Quarkus version 3.16.4, and also verified for version 3.17.x, when a request is done to our REST endpoints, the response body always returns the "content-encoding: gzip" when the header "accept-encoding" is sent in the request headers. While this happens, the body is not compressed.

Expected behavior

It should only return "content-encoding: gzip" when the body is gzipped.

Actual behavior

No response

How to Reproduce?

No response

Output of uname -a or ver

No response

Output of java -version

No response

Quarkus version or git rev

No response

Build tool (ie. output of mvnw --version or gradlew --version)

No response

Additional information

No response

[geoand]

Can you please attach a sample application that we can use to see the problem in action?

Thanks

[soaresGITHUB]

Can you please attach a sample application that we can use to see the problem in action?

Thanks

I should be able to do this over the weekend if that's fine.

[soaresGITHUB]

Can you please attach a sample application that we can use to see the problem in action?

Thanks

Hello, sorry for the delay in this. I've tried to replicate it on a project to attach here, but I've been unable to reproduce it.

It seems odd however that in our enterprise applications, simply reducing the Quarkus version to 3.13 was enough to mitigate this issue on our applications, but if I have some more free time towards the end of this sprint (or on my free time itself) I'll try and track it down a bit more so I can attach it here.

Thank you

[geoand]

Let's close for now since we don't have a reproducer. If one become available, we can reopen the issue and try to understand what's going on