-
Notifications
You must be signed in to change notification settings - Fork 24.3k
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Use existing character set in POST body when possible (#23603)
Summary: This commit fixes a bug introduced in a previous attempt (#23580) to address an issue where okhttp appended `charset=utf-8` to the Content-Type header when otherwise not specified. In that commit, I converted all characters to UTF-8, however it should instead use an existing encoding when possible. Related issues: #8237 (comment) [Android][fixed] - Respect existing character set when specified in fetch() POST request Pull Request resolved: #23603 Differential Revision: D14191750 Pulled By: hramos fbshipit-source-id: 11c1bfd98ccd33cd8e54ea426285b7d2ce9c2d7c
- Loading branch information
1 parent
c1349b5
commit 0d5aebb
Showing
2 changed files
with
96 additions
and
1 deletion.
There are no files selected for viewing
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
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