[
https://issues.apache.org/jira/browse/MESOS-6210?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15507085#comment-15507085
]
ASF GitHub Bot commented on MESOS-6210:
---------------------------------------
GitHub user drcrallen opened a pull request:
https://github.com/apache/mesos/pull/169
Add smarter master redirects.
* Fix MESOS-6210
* Any path after `/redirect` is now appended to the response
* Does not make any guarantees about non-path components of
the original request
* Updated docs to clarify this behavior.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/metamx/mesos MESOS-6210
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/mesos/pull/169.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #169
----
----
> Master redirect with suffix gets in redirect loop
> -------------------------------------------------
>
> Key: MESOS-6210
> URL: https://issues.apache.org/jira/browse/MESOS-6210
> Project: Mesos
> Issue Type: Bug
> Components: HTTP API
> Reporter: Charles Allen
> Labels: newbie
>
> Trying to go to a URI like
> {{http://SOME_MASTER:5050/master/redirect/master/frameworks}} ends up in a
> redirect loop.
> The expected behavior is to either not support anything after {{redirect}} in
> the path (redirect must be handled by a smart client), or to redirect to the
> suffix (redirect can be handled by a dumb client).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
