Networking: Preserve the content-type header when fetch()-ing #2028
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.
Allows the use of arbitrary Content-type header when sending POST requests from WordPress.
Playground fetch() network transport for
wp_safe_remote_*
calls enforced theContent-Type
header ofapplication/x-www-form-urlencoding
when POST-ing. This PR turns that value into a fallback that's only used if not explicit value is provided.Closes #1428
Testing instructions
text/plain