[
https://issues.apache.org/jira/browse/MESOS-6024?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15416033#comment-15416033
]
Charles Allen commented on MESOS-6024:
--------------------------------------
[~kaysoky] cool thanks
> CORS issue in 1.0.0 master UI
> -----------------------------
>
> Key: MESOS-6024
> URL: https://issues.apache.org/jira/browse/MESOS-6024
> Project: Mesos
> Issue Type: Bug
> Components: master, webui
> Affects Versions: 1.0.0
> Reporter: Charles Allen
>
> My setup is such that I have a dns entry which points to one of a group of
> mesos masters (3). The mesos masters are setup to use IP only stuff
> (advertise and bind based on ip address), and not try to do things based on
> hostname / DNS resolution.
> For example, I might have 3 masters 192.168.1.100, 192.168.1.101, and
> 192.168.1.103 behind master.mesos.internal
> Whenever I try and go to the "overall" dns endpoint, I get the error:
> XMLHttpRequest cannot load http://192.168.1.100:5050/master/state. No
> 'Access-Control-Allow-Origin' header is present on the requested resource.
> Origin 'http://master.mesos.internal:5050' is therefore not allowed access.
> And the page itself simply gives me the retry modal of "Failed to connect to
> master.mesos.internal:5050!"
> If I go to http://192.168.1.100:5050/ from the error message the whole web ui
> behaves as expected.
> Overall this is probably a good thing as I suspect proper security
> enforcement may have been lacking previously.
> The expected behavior is that I am redirected to the leader.
> This is on 1.0.0-2.0.89.ubuntu1404 from the mesosphere repository viewing
> with OSX Chrome 51.0.2704.103 (64-bit)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
