Add OData-Version header to requests #8288
Merged
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
ssoroka
approved these changes
Nov 6, 2020
ssoroka
pushed a commit
that referenced
this pull request
Nov 13, 2020
arstercz
pushed a commit
to arstercz/telegraf
that referenced
this pull request
Mar 5, 2023
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.
When using the redfish plugin against an HPE iLO4 host it fails parsing the responses. This is due to a backwards compatibility in iLO4 to before the standardization of field naming in embedded links. Setting the optional
OData-Versionon request headers signals the server to reply in a redfish 1.0 conformant format (https://hewlettpackard.github.io/ilo-rest-api-docs/ilo4/#redfish-1-0-conformance). This will not change the responses from already compliant hosts (tested against iDRAC)Required for all PRs:
Fixes #8093