Skip to content
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

Transfer-Encoding header is set twice #42238

Closed
FloGro3 opened this issue Jul 31, 2024 · 1 comment · Fixed by #43459
Closed

Transfer-Encoding header is set twice #42238

FloGro3 opened this issue Jul 31, 2024 · 1 comment · Fixed by #43459
Labels
area/rest kind/bug Something isn't working
Milestone

Comments

@FloGro3
Copy link

FloGro3 commented Jul 31, 2024

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.
image
image

How to Reproduce?

Here is a minimal project that reproduces the issue: https://github.com/FloGro3/response-header-issue-example

Output of uname -a or ver

No response

Output of java -version

Java version: 19.0.2

Quarkus version or git rev

3.12.3

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

Apache Maven 3.9.7

Additional information

No response

@FloGro3 FloGro3 added the kind/bug Something isn't working label Jul 31, 2024
@quarkus-bot
Copy link

quarkus-bot bot commented Jul 31, 2024

/cc @FroMage (resteasy-reactive), @stuartwdouglas (resteasy-reactive)

geoand added a commit to geoand/quarkus that referenced this issue Sep 24, 2024
@geoand geoand closed this as completed in 7005ab9 Sep 24, 2024
geoand added a commit that referenced this issue Sep 24, 2024
Make sure Transfer-Encoding set by a Resource is honored
@quarkus-bot quarkus-bot bot added this to the 3.16 - main milestone Sep 24, 2024
mskacelik pushed a commit to mskacelik/quarkus that referenced this issue Sep 27, 2024
@gsmet gsmet modified the milestones: 3.16.0.CR1, 3.15.2 Oct 18, 2024
gsmet pushed a commit to gsmet/quarkus that referenced this issue Oct 21, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/rest kind/bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants