Update Content Broker to Support non-GET Methods and Request Body (What…
Update Content Broker to Support non-GET Methods and Request Body
What changes are needed in order for this feature to work?
UI will include new fields
The HTTP Method. Supports all HTTP methods, the default should be GET since it's the most common method to retrieve content
Takes an optional request body for resources that require a request body
Need confirmation from Josh and Rex on this
Needs to support other HTTP methods and accept a request body
I created a PR in the content broker that tests and verifies this via POC. I can work off that or use that as a template when making the changes
What are the unknowns?
How can we prevent users from calling non-content-retrieval resources?
Create a whitelist that allows non-conventional methods to be passed in.
How should it be implemented?
Within the Content Broker
The default GET resource should already be accepted
How should the whitelist/blacklist look like?
What are the next steps?
Verify that the content broker can support non-GET methods and request bodies
This is done and confirmed, but this needs to be captured in the story for completeness
Get sign off on Josh and Rex on Dynamic Data diagram
I sent them a mockup, but I can always create a real demo via Hippo and send them that
I can create a new doc type so that I won't mess up current data structures
Get Josh and Rex on the same page on White/Blacklisting applications
This might be more of a Rex and I and then go to Josh for confirmation.