Transfer-Encoding header is set twice #42238
Comments
|
/cc @FroMage (resteasy-reactive), @stuartwdouglas (resteasy-reactive) |
geoand
added a commit
to geoand/quarkus
that referenced
this issue
Sep 24, 2024
geoand
added a commit
that referenced
this issue
Sep 24, 2024
Make sure Transfer-Encoding set by a Resource is honored
mskacelik
pushed a commit
to mskacelik/quarkus
that referenced
this issue
Sep 27, 2024
gsmet
pushed a commit
to gsmet/quarkus
that referenced
this issue
Oct 21, 2024
Closes: quarkusio#42238 (cherry picked from commit 7005ab9)
bschuhmann
pushed a commit
to bschuhmann/quarkus
that referenced
this issue
Nov 16, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
In our BFFs we found out that when receiving a response from the backend that has "Transfer-Encoding" header set to "chunked" and we forward this response to the FE suddenly there are two "Transfer-Encoding" headers present which are set to "chunked". The browser is ignoring this but some rest clients are throwing an error because of theses duplicate headers.
Expected behavior
"Transfer-Encoding" header is only present once in the response of the bff.
Actual behavior
"Transfer-Encoding" header is set twice.
How to Reproduce?
Here is a minimal project that reproduces the issue: https://github.com/FloGro3/response-header-issue-example
Output of
uname -aorverNo response
Output of
java -versionJava version: 19.0.2
Quarkus version or git rev
3.12.3
Build tool (ie. output of
mvnw --versionorgradlew --version)Apache Maven 3.9.7
Additional information
No response
The text was updated successfully, but these errors were encountered: