This repository has been archived by the owner on Dec 4, 2024. It is now read-only.
Follow standby redirects #594
Comments
|
@timcharper I can send a PR for this. Can you link me to a relevant Marathon PR or commit? I tried looking but I couldn't find any! |
|
@timcharper NVM, found it. Original Marathon JIRA card → https://jira.mesosphere.com/projects/MARATHON/issues/MARATHON-7178 Marathon PR → d2iq-archive/marathon#6211 |
|
@timcharper Also, FYI, the code in your branch returns a
|
|
@paambaati Thanks for the clarification! |
timcharper
pushed a commit
that referenced
this issue
Aug 3, 2018
Marathon 1.7.x returns a 302 redirect response from a non-leader. So we make sure Marathon-lb can follow it to the leader. Related Marathon JIRA card: https://jira.mesosphere.com/projects/MARATHON/issues/MARATHON-7178 Fixes #594
cybernaut613
pushed a commit
to inbaytech/marathon-lb
that referenced
this issue
Apr 23, 2020
Marathon 1.7.x returns a 302 redirect response from a non-leader. So we make sure Marathon-lb can follow it to the leader. Related Marathon JIRA card: https://jira.mesosphere.com/projects/MARATHON/issues/MARATHON-7178 Fixes d2iq-archive#594
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
In Marathon 1.7.x, Marathon will be sending 302 redirect responses when requesting /v2/events from a non-leader. Marathon-lb needs to be updated to follow these redirects.
The text was updated successfully, but these errors were encountered: