[
https://issues.apache.org/jira/browse/SLIDER-738?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14267760#comment-14267760
]
Jonathan Maron commented on SLIDER-738:
---------------------------------------
The URI for the redirect would be obtained as data in the registry. Assuming
the data in question is written by the AM and the appropriate permissions/ACL
are applied I'm not certain spoofing is as much of an issue (i.e. it is in
effect internally generated)
> (protototype) Registry REST API to serve up 302 redirects to service endpoints
> ------------------------------------------------------------------------------
>
> Key: SLIDER-738
> URL: https://issues.apache.org/jira/browse/SLIDER-738
> Project: Slider
> Issue Type: Sub-task
> Components: registry, Web & REST
> Affects Versions: Slider 0.60
> Reporter: Steve Loughran
> Assignee: Steve Loughran
> Original Estimate: 3h
> Remaining Estimate: 3h
>
> extend the REST view of the registry so that you can ask for a specific api
> of a service endpoint, and optionally for the response to be a 302 to the
> chosen destination.
> e.g.
> {code}
> GET
> services/org.apache.slider/app1/?api=http://org.apache.slider/registry&format=redirect
> {code}
> this would look up the API, 404 if not there, and that provided the address
> format is a URI, return a (random) choice of one of the listed instances as a
> 302 redirect.
> The benefit here is that you can bookmark an entry, or use curl without
> having to parse the resulting JSON at all -it is all processed server-side
> +tests
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
