You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
The text was updated successfully, but these errors were encountered:
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
orver
No response
Output of
java -version
No response
Quarkus version or git rev
No response
Build tool (ie. output of
mvnw --version
orgradlew --version
)No response
Additional information
No response
The text was updated successfully, but these errors were encountered: