HomeMesosphereNo notifications. 4 unresolved issues.

accepting wildcard for ping to enable previous behavior for 1.4
ClosedAll Users

Authored by kensipe on Jun 29 2017, 8:55 PM.

Diff Detail

Repository
rMARATHON marathon
Branch
ken/wild-ping-1.4
Lint
No Linters Available
Unit
No Unit Test Coverage
Build Status
Buildable 3026
Build 5756: Marathon (revised)Jenkins
Build 5755: arc lint + arc unit
kensipe created this revision.Jun 29 2017, 8:55 PM
jenkins requested changes to this revision.Jun 29 2017, 8:55 PM
This revision now requires changes to proceed.Jun 29 2017, 8:55 PM
ichernetsky accepted this revision.Jun 29 2017, 8:59 PM
jenkins accepted this revision.Jun 29 2017, 9:09 PM
This revision is now accepted and ready to land.Jun 29 2017, 9:09 PM
✔ Build of 3675 completed jenkins-public-marathon-phabricator-392.

You can create a DC/OS with your patched Marathon by creating a new pull
request with the following changes in buildinfo.json:

"url": "https://downloads.mesosphere.io/marathon/snapshots/marathon-1.5.0-SNAPSHOT-627-gc392203.tgz",
"sha1": "1152f2b4b4e3ba22f6875e8cb59541189048f9dd"

\\ ٩( ᐛ )و //

ajain13 accepted this revision.Jun 30 2017, 3:12 AM
kensipe closed this revision.Jun 30 2017, 6:50 PM
jdef added a comment.Jul 4 2017, 4:01 PM

We might want a change log entry for this

jeschkies added inline comments.Jul 4 2017, 4:19 PM
src/main/scala/mesosphere/marathon/api/SystemResource.scala
40

I think this is a breaking change. We had a customer whose ping broke: https://jira.mesosphere.com/browse/MARATHON_EE-1522. Would wildcard work them?

jdef added a comment.Jul 4 2017, 5:09 PM

I made assumptions in my initial review that appear to be false.

I spent some time this morning refreshing on http content negotiation and the use of wildcard. I can't actually find any valid use case for a server returning a wildcard content type, only that clients may accept wildcard. A server could add a "Vary: *" header to mitigate caching, but that's independent of content type.

We might actually want to revert this change since, upon second look, it appears harmful because it's outside the http spec.