Fix issue #630: Unable to override Content-Type header charset #750
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.
Fix: Prevent automatic charset=utf-8 addition to Content-Type headers
Issue
When sending requests with Content-Type headers like "application/json", the Dart HTTP library automatically appends "charset=utf-8" to the header value. Some APIs reject requests with this charset specification, but users currently have no way to prevent this behavior.
Fixes #630 by giving users control over Content-Type headers.
Changes
useRawContentType
boolean field toHttpRequestModel
Implementation Details
useRawContentType
is true, Content-Type headers are sent without charsetTesting Instructions
Related Issues
charset
toContent-Type
header dart-lang/http#1438