Use application/json in request headers #145
Open
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
p-schneider
force-pushed
the
patch-http-request-headers
branch
from
1092840 to
36854ca
Compare
Chris53897
added a commit
to Chris53897/Phue
that referenced
this pull request
Aug 14, 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.
Using Wireshark I realized the curl adapter sends the
Content-Type: application/x-www-form-urlencodedheader by default when sending a body/payload in the HTTP Request.The Request body is json, so it should be marked as such, even if the Hue Bridge is "stupid enough" to accept the invalid combination of header and payload.
Also prevents this Deprecation Warning: