Adding Content-Type headers to POST and PATCH requests #23
Conversation
This file contains hidden or 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
|
Hey @ctgowrie. Thanks for this - look like a nice simple improvement (and well spotted). |
|
@dglsparsons Thanks! I can move the |
|
@ctgowrie That sounds like a good plan! I imagine pretty much every request is JSON with the sole exception of the file uploads. |
…, nil for body of GET, DELETE
dglsparsons
approved these changes
Apr 25, 2022
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.
While working on some API improvements, I noticed that requests from the terraform provider do not set the content-type header, so this adds Content-Type to all POST and PATCH requests where relevant.