mesos-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "haosdent (JIRA)" <>
Subject [jira] [Commented] (MESOS-5911) Webui redirection to leader in browser does not work
Date Thu, 28 Jul 2016 01:14:21 GMT


haosdent commented on MESOS-5911:

Redirect to the leader before loading UI sounds good to me as well. We need redirect when
user type


For some requests like {{metrics/snapshot}} and {{health}}, we may not want to redirect when
current master is not the leader. 

> Webui redirection to leader in browser does not work
> ----------------------------------------------------
>                 Key: MESOS-5911
>                 URL:
>             Project: Mesos
>          Issue Type: Bug
>    Affects Versions: 1.0.0
>            Reporter: Jacob Janco
>            Assignee: haosdent
>            Priority: Blocker
>              Labels: webui
>         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):
> 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'

This message was sent by Atlassian JIRA

View raw message