Uploaded image for project: 'Bitbucket Data Center'
  1. Bitbucket Data Center
  2. BSERV-4250

REST json response does not match the configured Base URL

    XMLWordPrintable

Details

    • Bug
    • Resolution: Fixed
    • Low
    • 2.12.0
    • 2.10.0
    • API - REST
    • JIRA: 6.1.5
      Stash: 2.10.0
      JDK: Oracle 1.7.0_45
      OS: Debian GNU/Linux 7.3

    Description

      As explained in the issue JRA-35413, the json response given by Stash does not match the configured Base URL when hitting stashinstance/stash/rest/capabilities/navigation.

      While trying to create a branche from JIRA, it results to a call to the wrong address within the user's browser. As rsmart says as designed for JIRA:

      The URL that create branch uses is given to it by stash (its baseURL in the json response at: stashinstance/rest/capabilities/navigation)

      Here is my configuration:

      When trying to create a branch from JIRA, the instance hit http://localhost:7990/stash/rest/capabilities/navigation, the JSON answer is:

      {
          "create-branch":[{
                  "href": "http://localhost:7990/stash/plugins/servlet/create-branch",
                  "label": "Stash",
                  "icon": "http://localhost:7990/stash/plugins/servlet/create-branch/icon.png",
                  "tooltip": "",
                  "lang": "en-GB",
                  "weight":300
              }]
      }
      

      After rsmart comment here, it seems the JSON answer from the Stash instance should always be as configured in the Stash instance Base URL:

      "href": "https://full.stash.address.com/stash/plugins/servlet/create-branch"

      Attachments

        Issue Links

          Activity

            People

              pepoirot Pierre-Etienne Poirot (Inactive)
              19a9a55f6180 Luc Calaresu
              Votes:
              0 Vote for this issue
              Watchers:
              11 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: