Uploaded image for project: 'Marathon'
  1. Marathon
  2. MARATHON-8200

Content negotiation randomly chooses text/plain for tasks endpoints when no priorities provided by client

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Medium
    • Resolution: Done
    • Affects Version/s: None
    • Fix Version/s: DC/OS 1.11.3
    • Component/s: None
    • Labels:
      None

      Description

      HTTP allows content-types to have priorities assigned via the attribute "qs", and the spec allows a value between 0 and 1. We had to remove it for when upgrading to Jersey 2.27.

      The documentation mentioned the fix was for web browsers. I checked the web browsers and they all continued to work, and the integration tests passed, so went ahead and merged.

      However, turns out the failure was a bit random. We need to deprioritize text/plain

        Attachments

          Activity

            People

            • Assignee:
              tharper Tim Harper
              Reporter:
              tharper Tim Harper
              Team:
              Orchestration Team
              Watchers:
              Tim Harper
            • Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: