[
https://issues.apache.org/jira/browse/MESOS-3832?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15099093#comment-15099093
]
Kapil Arya commented on MESOS-3832:
-----------------------------------
Let's see if [[email protected]] can commit it.
> Scheduler HTTP API does not redirect to leading master
> ------------------------------------------------------
>
> Key: MESOS-3832
> URL: https://issues.apache.org/jira/browse/MESOS-3832
> Project: Mesos
> Issue Type: Bug
> Components: HTTP API
> Affects Versions: 0.24.0, 0.24.1, 0.25.0
> Reporter: Dario Rexin
> Assignee: Vinod Kone
> Labels: newbie
>
> The documentation for the Scheduler HTTP API says:
> {quote}If requests are made to a non-leading master a “HTTP 307 Temporary
> Redirect” will be received with the “Location” header pointing to the leading
> master.{quote}
> While the redirect functionality has been implemented, it was not actually
> used in the handler for the HTTP api.
> A probable fix could be:
> - Check if the current master is the leading master.
> - If not, invoke the existing {{redirect}} method in {{src/master/http.cpp}}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
