Match Content-Type charset case-insensitively #440
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 connect handler returns http.StatusUnsupportedMediaType when a request has a
Content-Type: application/json; charset=UTF-8
header. However, according to RFC 9110 Section 8.3.2, the charset parameter value should be treated as case-insensitive.In this PR, I have modified the charset parameter value for user requests and acceptable content types of handlers to all be handled in lowercase.