Details
-
Story
-
Resolution: Unresolved
-
Major
-
None
-
None
-
None
-
None
-
-
Empty show more show less
-
Yes
-
Yes
Description
User Story
As a developer, I want to call REST Clients from a browser or other frontend in a way that does not expose which endpoint I am hitting or any secrets or authentication information, so that I can use my configured REST clients, and so that they are secure, and to overcome any potential CORS issues.
Alternative Title
"Use a REST client via REST" ![]()
Acceptance Criteria:
- Dev can make HTTP request from a frontend to the Magnolia server to trigger a Magnolia REST client.
- Any headers and cookies will be sent along.
- The complete response from the final endpoint will be returned, including headers and cookies.
- By default the REST client cache will be respected, but there must be a convenient way to disable the cache on a call.
- The proxy might be available under a path like /.proxy, or it might be considered a kind of REST endpoint and be available under /.rest.
- Should be easy to setup. (Not sure if its a property on a REST client, or if it is a configurable REST Endpoint that then references a REST client.
- Developer can choose the name that is exposed. By default it would be the name of the REST client.
Notes
resfn allows devs to use REST clients from templates. This feature allows devs to conveniently use REST Client in a headless context.
This can essentially be done currently by writing an FTL template which calls the REST Client via restfn. This ticket would make the feature more robust and simpler to setup and use.
Checklists
Acceptance criteria