feat(graphql): forces http header value to be lowercase #1237
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.
While RFC2616 indicates http header field
names
are case insensitive, it leaves http header fieldvalues
more open to interpretation, such as using the textThis is a small user experience improvement for REST Client users to prevent a negative experience by using a case sensitive value.
This is also consistent with the current code snippet for getHeader method which forces lowercase on the http header fields.
vscode-restclient/src/utils/misc.ts
Line 12 in 80ee7d1
fixes #1236