Add ability to handle non-JSON endpoints #24
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
|
oh! love the MR, I kinda missed this. will try to resolve the conflicts soon :) |
Add an option to pass arbitrary HTTP request headers in the `raw` command, for endpoints such as `[app]/sso/saml/metadata` that are not JSON. Also do not attempt to parse the body as JSON if the content type indicates something other than JSON.
aogail
force-pushed
the
feature/handleNonJsonEndpoints
branch
from
a7bbc66 to
60f3357
Compare
|
Hi @flypenguin, I rebased onto the current main to resolve the conflicts. |
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.
Add an option to pass arbitrary HTTP request headers in the
rawcommand, for endpoints such as[app]/sso/saml/metadatathat are not JSON. Also do not attempt to parse the body as JSON if the content type indicates something other than JSON.Example usage: