KTOR-7934 Remove Content-Length for browser #4621
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
bjhham
force-pushed
the
bjhham/content-length-browser-fix
branch
from
fb4e99b to
359f2fc
Compare
bjhham
force-pushed
the
bjhham/content-length-browser-fix
branch
from
359f2fc to
d865f73
Compare
e5l
approved these changes
Jan 24, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Subsystem
Client, Js
Motivation
KTOR-7934 JS/WASM fails with "IllegalStateException: Content-Length mismatch" on requesting gzipped content
Solution
Requests from the browser will always remove the Content-Encoding and Content-Length headers. This is because Content-Encoding can be stripped by the browser while an inaccurate Content-Length remains. This depends on the server, but is common based on the CORS policy.