fix(core): Handling content encoding correctly #3907
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
Signed-off-by: Xuanwo <github@xuanwo.io>
Young-Flash
approved these changes
Jan 4, 2024
Zheaoli
reviewed
Jan 4, 2024
| let content_length = if is_head { | ||
| // | ||
| // - If the request method is HEAD, we will ignore content length. | ||
| // - If response contains content_encoding, we should omit it's content length. |
There was a problem hiding this comment.
I propose that update the comment to mention that this trick would only be available in WASM32
There was a problem hiding this comment.
Welcome to submit a PR to improve it 💌
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.
no_gzip&gzipnot supported for wasm target seanmonstar/reqwest#2073I tested locally with gdrice. We should extend the wasm tests to all available services in the future.