[MESOS-3902] The Location header when non-leading master redirects to leading master is incomplete.

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 0.25.0
• Fix Version/s: 1.0.0
• Component/s: HTTP API, master
• Labels: uber

Environment

3 masters, 10 slaves

• Epic Link: Scheduler API v1 improvements
• Assignee: Ashwin Murthy
• Reporter: Ben Whitehead
• Created: 11/Nov/15 23:04
• Updated: 31/May/16 02:11
• Resolved: 25/Mar/16 17:23

Description

The master now sets a location header, but it's incomplete. The path of the URL isn't set. Consider an example:

> cat /tmp/subscribe-1072944352375841456 | httpp POST 127.1.0.3:5050/api/v1/scheduler Content-Type:application/x-protobuf
POST /api/v1/scheduler HTTP/1.1
Accept: application/json
Accept-Encoding: gzip, deflate
Connection: keep-alive
Content-Length: 123
Content-Type: application/x-protobuf
Host: 127.1.0.3:5050
User-Agent: HTTPie/0.9.0



+-----------------------------------------+
| NOTE: binary data not shown in terminal |
+-----------------------------------------+

HTTP/1.1 307 Temporary Redirect
Content-Length: 0
Date: Fri, 26 Feb 2016 00:54:41 GMT
Location: //127.1.0.1:5050

Issue Links

• is duplicated by: MESOS-3832 Scheduler HTTP API does not redirect to leading master
• relates to: MESOS-2976 Allow create multi master in test cases