This repository has been archived by the owner on Mar 13, 2021. It is now read-only.
Handle Content-Type headers with a charset #30
Merged
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.
The Content-Type header can also contain a charset param.
Content-Type: text/plain; charset=utf-8
Previously this would cause the gRPC handler to choke. Now the charset
is ignored. In the future we should correctly parse the charset and
decode the payload accordingly. For now, all text content is assumed to
be utf-8.
Fixes: #29