Don't expect Contet-Type header to exactly match application/json
#10560
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
yhabteab
added
bug
yhabteab
added
the
consider backporting
yhabteab
force-pushed
the
influxdb-mist
branch
4 times, most recently
from
d894012 to
d8d5622
Compare
InfluxDB seems to always include some other metadata in the `Content-Type` header separated by semicolons like `application/json; charset=utf-8`, and comparing the whole string with `application/json` will always fail, resulting in almost always useless warnings without any helpful information for the user what actually went wrong.
yhabteab
force-pushed
the
influxdb-mist
branch
from
d8d5622 to
5cf70a2
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
InfluxDB seems to always include some other metadata in the
Content-Typeheader separated by semicolons likeapplication/json; charset=utf-8, and comparing the whole string withapplication/jsonwill always fail, resulting in almost always useless warnings without any helpful information for the user what actually went wrong.fixes #10072
ref/IP/60981