Use charset from response Content-Type header to decode #1302
Merged
Conversation
kdavisk6
requested changes
Nov 3, 2020
kdavisk6
approved these changes
Jan 8, 2021
velo
pushed a commit
that referenced
this pull request
Oct 7, 2024
* If charset is set in Content-type, we decode response using that charset * Java 8 compatibility * Format fix * Moving code to get charset to Response in order to be used by another decoders
velo
pushed a commit
that referenced
this pull request
Oct 8, 2024
* If charset is set in Content-type, we decode response using that charset * Java 8 compatibility * Format fix * Moving code to get charset to Response in order to be used by another decoders
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Sometimes charset from response is not UTF-8, then if charset is informed in Content-type header, this charset is used to decode