Skip to content

Add ability to handle non-JSON endpoints#24

Open
aogail wants to merge 1 commit into
flypenguin:mainfrom
aogail:feature/handleNonJsonEndpoints
Open

Add ability to handle non-JSON endpoints#24
aogail wants to merge 1 commit into
flypenguin:mainfrom
aogail:feature/handleNonJsonEndpoints

Conversation

@aogail
Copy link
Copy Markdown

@aogail aogail commented Jan 5, 2024

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.

Example usage:

$ okta-cli raw -H 'Accept: application/xml' 'apps/id/sso/saml/metadata'
<?xml version="1.0" encoding="UTF-8"?><md:EntityDescriptor entityID="http://www.okta.com/...

@flypenguin
Copy link
Copy Markdown
Owner

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 aogail force-pushed the feature/handleNonJsonEndpoints branch from a7bbc66 to 60f3357 Compare May 20, 2024 21:34
@aogail
Copy link
Copy Markdown
Author

aogail commented May 20, 2024

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants