Handle empty or falsy charset in response#1928
Merged
Merged
Conversation
Contributor
|
Why? |
Contributor
Author
|
@hueniverse Personally I would like to serve |
Contributor
Author
|
Any update on this? Also, https://tools.ietf.org/html/rfc6838#section-4.2.1 states that the charset "SHOULD NOT" be specified for text content where the charset is already transported in the payload. |
hueniverse
pushed a commit
that referenced
this pull request
Oct 1, 2014
Handle empty or falsy charset in response
|
This thread has been automatically locked due to inactivity. Please open a new issue for related bugs or questions following the new issue template instructions. |
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
This way it's possible to explicitly remove the charset from the response which can be valid for some use-cases.