http resource: use proper syntax in curl header option
#2285
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
`curl` expects a valid header per RFC 2616 when using the `-H`/`--header` option. RFC 2616 declares header field/values should be separated using a colon (`:`): https://tools.ietf.org/html/rfc2616#section-4.2 Signed-off-by: Seth Chisamore <schisamo@chef.io>
|
Ugh, I'm an idiot, that's my fault. Thanks for the fix, @schisamo. |
adamleff
changed the title
curl header optioncurl header option
adamleff
approved these changes
Nov 3, 2017
|
Please backport that fix to 1.51 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
curlexpects a valid header per RFC 2616 when using the-H/--headeroption. RFC 2616 declares header field/values should be separated using a colon (:):https://tools.ietf.org/html/rfc2616#section-4.2
Signed-off-by: Seth Chisamore schisamo@chef.io