You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@mesos.apache.org by "Barry Kaplan (JIRA)" <ji...@apache.org> on 2016/08/22 04:11:20 UTC

[jira] [Comment Edited] (MESOS-5911) Webui redirection to leader in browser does not work

    [ https://issues.apache.org/jira/browse/MESOS-5911?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15430015#comment-15430015 ] 

Barry Kaplan edited comment on MESOS-5911 at 8/22/16 4:10 AM:
--------------------------------------------------------------

Never mind, I did not notice the fix was for 1.0.1.

--Reading this I cannot tell what the fix was. After upgrading to 1.0.0 I can only open the UI on the leader. I get--

XMLHttpRequest cannot load http://10.0.139.65:5050/master/state. No 'Access-Control-Allow-Origin' header is present on the requested resource. Origin 'http://s-mesos-master-1.use1.systeminsights.com:5050' is therefore not allowed access.--


was (Author: memelet):
Reading this I cannot tell what the fix was. After upgrading to 1.0.0 I can only open the UI on the leader. I get 

XMLHttpRequest cannot load http://10.0.139.65:5050/master/state. No 'Access-Control-Allow-Origin' header is present on the requested resource. Origin 'http://s-mesos-master-1.use1.systeminsights.com:5050' is therefore not allowed access.

> Webui redirection to leader in browser does not work
> ----------------------------------------------------
>
>                 Key: MESOS-5911
>                 URL: https://issues.apache.org/jira/browse/MESOS-5911
>             Project: Mesos
>          Issue Type: Bug
>          Components: webui
>    Affects Versions: 1.0.0
>            Reporter: Jacob Janco
>            Assignee: haosdent
>            Priority: Blocker
>              Labels: webui
>             Fix For: 1.0.1
>
>         Attachments: http_redirect.gif
>
>
> We deployed 1.0.0-rc4 in a small test cluster with 3 masters/5 agents. Redirection to master curling for state.json returned the expected 307, however, in browser (chrome/safari/firefox), redirection failed with: 
> {code}
> XMLHttpRequest cannot load <master_url_1>:5050/master/state. No 'Access-Control-Allow-Origin' header is present on the requested resource. Origin '<master_url_2>:5050' is therefore not allowed access.
> {code}
> This is the patch that introduced the redirect on /state (and HTTP calls): https://reviews.apache.org/r/34646
> The issue is that before this change, the server side does not redirect, the web UI controller.js decides from the content of the state.json which leader to redirect and then invoke redirection itself. Browsers allow this but not the server side initiated redirect without 'Access-Control-Allow-Origin' header?



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)