-
Bug
-
Resolution: Done-Errata
-
Major
-
3.8.5.GA
This bug was discovered by TD created for QUARKUS-4538.
I realized this issue doing the test coverage for sending different payloads with gzip compression enabled and the property 'quarkus.resteasy.gzip.max-input' set.
My test coverage file –> https://github.com/jcarranzan/quarkus-test-suite/blob/fc226515cd086c84d45f464fc8fab0a8737912ee/http/http-advanced/src/test/java/io/quarkus/ts/http/advanced/GzipMaxInputIT.java
The tests passed ok in our CI jobs environment except for native mode.
If you executed the maven command, the test failed
mvn clean verify -Pnative -Dit.test=GzipMaxInputIT
Log error:
10:56:43,333 INFO ## Running test GzipMaxInputIT.sendMaximumAllowedPayload() 10:56:45,706 INFO [app] Service stopped (Quarkus NATIVE mode) [ERROR] Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 7.432 s <<< FAILURE! -- in io.quarkus.ts.http.advanced.GzipMaxInputIT [ERROR] io.quarkus.ts.http.advanced.GzipMaxInputIT.sendMaximumAllowedPayload -- Time elapsed: 0.356 s <<< FAILURE! org.opentest4j.AssertionFailedError: The response should be 200 OK because sending just the limit payload configured using quarkus.resteasy.gzip.max-input=100M. This fails if the suffix format parsing is not working and RESTEasy falls back to its default which is 10M ==> expected: <200> but was: <413> at org.junit.jupiter.api.AssertionFailureBuilder.build(AssertionFailureBuilder.java:151) at org.junit.jupiter.api.AssertionFailureBuilder.buildAndThrow(AssertionFailureBuilder.java:132) at org.junit.jupiter.api.AssertEquals.failNotEqual(AssertEquals.java:197) at org.junit.jupiter.api.AssertEquals.assertEquals(AssertEquals.java:150) at org.junit.jupiter.api.Assertions.assertEquals(Assertions.java:563) at io.quarkus.ts.http.advanced.GzipMaxInputIT.sendMaximumAllowedPayload(GzipMaxInputIT.java:68) at java.base/java.lang.reflect.Method.invoke(Method.java:568) at java.base/java.util.ArrayList.forEach(ArrayList.java:1511) at java.base/java.util.ArrayList.forEach(ArrayList.java:1511)
On the other hand, it's solved by the fix: https://github.com/quarkusio/quarkus/pull/41054
- links to
-
RHSA-2024:6437
Red Hat build of Quarkus 3.8.6 release and security update
