[
https://issues.apache.org/jira/browse/MESOS-5911?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15396723#comment-15396723
]
haosdent commented on MESOS-5911:
---------------------------------
Hi, [~vinodkone] [~xujyan] We could not
{code}
do a client side redirect in the `http.get.failure()` callback
{code}
Because the silent (transparent) redirection is the part of [XMLHttpRequest
specification |
https://www.w3.org/TR/XMLHttpRequest/#same-origin-request-event-rules] when get
307. We could not stop or inspect the request when the response status code is
307, because the browser would follow the redirection automatically no matter
what.
Then in {{http.get.failure()}}, we only have the knowledge about the request
failed. But we don't know why it failed. The request may fail because of the
bad network. On the other side, we don't know the leading master in this case,
so we could not pop up a dialog with a button redirect to the leader. cc
[~mlunoe] [~greggomann] [~anandmazumdar]
> 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
> 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):
> 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)
