Details

    • Type: Task
    • Status: Resolved
    • Resolution: Done
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: None
    • Labels:

      Description

      With Marathon 0.14.0-RC1 (mesosphere/marathon docker container was used) the endpoints in the details page of an application's task are prefixing the URL with // instead of http://, which causes it to let the browser choose the HTTP/HTTPS scheme depending on how you serve the Marathon web interface.

      In our case we serve Marathon over SSL, that is, the https scheme, but the services we spawn are exposing HTTP (no SSL), and as configured in the health checks - HTTP.

      As a fix, the Marathon task's detail page must not use // to to auto-select the scheme depending on marathon's view but hard-wire it down the the configured protocol, that is, http://$HOST:$PORTn/

        Attachments

          Activity

            People

            • Assignee:
              Unassigned
              Reporter:
              christianparpart Christian Parpart
              Team:
              Orchestration Team
              Watchers:
            • Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: