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
Resteasy Reactive adds transfer-encoding header though content-length is present #26464
Comments
/cc @FroMage, @geoand, @stuartwdouglas |
quarkus-bot
bot
added
area/resteasy-reactive
env/windows
Impacts Windows machines
labels
Jun 30, 2022
Thanks for the reproducer. I totally agree the behavior is not correct, looking into it now |
geoand
added a commit
to geoand/quarkus
that referenced
this issue
Jun 30, 2022
#26467 takes care of the issue |
geoand
added a commit
that referenced
this issue
Jun 30, 2022
Properly ensure that transfer-encoding is not set when content-length exists
gsmet
pushed a commit
to gsmet/quarkus
that referenced
this issue
Jul 4, 2022
… exists Fixes: quarkusio#26464 (cherry picked from commit 8cf8d61)
gsmet
pushed a commit
to gsmet/quarkus
that referenced
this issue
Jan 13, 2023
… exists Fixes: quarkusio#26464 (cherry picked from commit 8cf8d61)
gsmet
pushed a commit
to gsmet/quarkus
that referenced
this issue
Jan 25, 2023
… exists Fixes: quarkusio#26464 (cherry picked from commit 8cf8d61)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
I want to stream filedownloads. The filesize is already known (stored in db on upload).
The filesize is important to me, since I can use it as content-length header, which allows the browser to show a progress bar for the download instead of just spinning.
e.g.
Without the content-length header, browser would simply show a spinning progress.
In resteasy-classic, this worked without problems.
In resteasy-reactive however, I found that the "Transfer-Encoding: Chunked" header is always added to the response when I am stream, even though I manually set content-length.
According to the RFC 2616, this behaviour is not allowed.
https://greenbytes.de/tech/webdav/rfc2616.html#rfc.section.4.4
Expected behavior
No Transfer-Encoding header is present if a content-length was already manually set.
The response should still be streamed.
Actual behavior
How to Reproduce?
Reproducer:
transfer-encoding-clash.zip
Output of
uname -a
orver
Microsoft Windows [Version 10.0.19044.1766]
Output of
java -version
openjdk 18.0.1 2022-04-19 OpenJDK Runtime Environment Temurin-18.0.1+10 (build 18.0.1+10) OpenJDK 64-Bit Server VM Temurin-18.0.1+10 (build 18.0.1+10, mixed mode, sharing)
GraalVM version (if different from Java)
No response
Quarkus version or git rev
2.10.1.Final
Build tool (ie. output of
mvnw --version
orgradlew --version
)Apache Maven 3.8.4 (9b656c72d54e5bacbed989b64718c159fe39b537) Maven home: C:\eclipse\tools\java\maven Java version: 18.0.1, vendor: Eclipse Adoptium, runtime: C:\eclipse\tools\java\18 Default locale: de_DE, platform encoding: UTF-8 OS name: "windows 10", version: "10.0", arch: "amd64", family: "windows"
Additional information
No response
The text was updated successfully, but these errors were encountered: