♻ Assume request bodies contain JSON when no Content-Type header is provided #3456
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.
♻ Assume request bodies contain JSON when no Content-Type header is provided
This is related to #2118 and the CVE GHSA-8h2j-cgx8-6xv7 about CSRF.
Some clients already assume that request bodies are read as JSON, even when no content-type header is set: #2118 (comment)
And the risk of CSRF only applies for specific Content-Type headers, so, no Content-Type header is already protected from CORS preflights: https://developer.mozilla.org/en-US/docs/Web/HTTP/CORS#simple_requests