[
https://issues.apache.org/jira/browse/MESOS-2131?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14218580#comment-14218580
]
Cody Maloney commented on MESOS-2131:
-------------------------------------
`/proxy/{name}` would be nice, but unfortunately the way that libprocess' route
handling works, making that case work correctly would require more
restructuring than what my current prefix patch does. The /proxy/ is eaten by
libprocess in a different dispatch than what the rest of it is consumed by, and
there are some particular special cases for local file assets, forwarding to
other libprocesses if you just provide a UPID rather than a port, and various
other not well documented things I'd rather not disturb.
> Add a reverse proxy endpoint to mesos
> -------------------------------------
>
> Key: MESOS-2131
> URL: https://issues.apache.org/jira/browse/MESOS-2131
> Project: Mesos
> Issue Type: Improvement
> Components: master, slave
> Reporter: Cody Maloney
> Assignee: Cody Maloney
> Priority: Minor
>
> A new libprocess Process inside mesos which allows attaching/detaching known
> endpoints at a specific path.
> Ideally I want to be able to do things like attach 'slave-id' and pass HTTP
> requests on to that slave:
> Sample endpoint actions:
> C++ api:
> attach(std::string name, Node target): Add a new reverse proxy path
> detach(std::string name): Remove an established reverse proxy path
> HTTP endpoints:
> /proxy/go/{name}
> - Prefix matches a path, forwards the remaining path onto the remote endpoin
> /proxy/debug.json
> - Prints out all attached endpoints.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
