Case-insensitive check for content type before setting it #18
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.
Updated
tests/test-headers.js
to test for the case this PR addresses.If the following conditions were met it would result in the content-type header always being "text/plain;charset=UTF-8":
I encountered it when sending a POST request with
xhr.setRequestHeader('content-type', 'application/x-www-form-urlencoded');
, then was surprised by the server receiving the content-type astext/plain
.