[
https://issues.apache.org/jira/browse/MESOS-3796?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jeffrey Schroeder updated MESOS-3796:
-------------------------------------
Description:
There are several places where it would be useful to access the mesos master
api (http port 5050) or agent api (http port 5051) via a javascript client.
This is inhibited by the fact that the http headers such as
Access-Control-Allow-Origin are not passed at all by mesos. A stop-gap is to
write a small proxy which passes requests to/from mesos while adding the
header, but that is suboptimal for several reasons.
Allowing the option to configure said headers, or just to enable them
explicitly would be very useful. Some projects such as mesos-ui[1] have an
issue open about this[2].
[1] http://capgemini.github.io/devops/mesos-ui/
[2] https://github.com/Capgemini/mesos-ui/issues/57
was:
There are several places where it would be useful to access the mesos master
api (http port 5050) or agent api (http port 5051) via a javascript client.
This is inhibited by the fact that the http headers such as
Access-Control-Allow-Origin are not passed at all by mesos.
Allowing the option to configure said headers, or just to enable them
explicitly would be very useful. Some projects such as mesos-ui[1] have an
issue open about this[2].
[1] http://capgemini.github.io/devops/mesos-ui/
[2] https://github.com/Capgemini/mesos-ui/issues/57
> Mesos Master and Agent http api should support configurable CORS headers
> ------------------------------------------------------------------------
>
> Key: MESOS-3796
> URL: https://issues.apache.org/jira/browse/MESOS-3796
> Project: Mesos
> Issue Type: Improvement
> Components: HTTP API
> Affects Versions: 0.25.0
> Reporter: Jeffrey Schroeder
> Priority: Minor
>
> There are several places where it would be useful to access the mesos master
> api (http port 5050) or agent api (http port 5051) via a javascript client.
> This is inhibited by the fact that the http headers such as
> Access-Control-Allow-Origin are not passed at all by mesos. A stop-gap is to
> write a small proxy which passes requests to/from mesos while adding the
> header, but that is suboptimal for several reasons.
> Allowing the option to configure said headers, or just to enable them
> explicitly would be very useful. Some projects such as mesos-ui[1] have an
> issue open about this[2].
> [1] http://capgemini.github.io/devops/mesos-ui/
> [2] https://github.com/Capgemini/mesos-ui/issues/57
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
