Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-64143

Test results not loaded for branches with slash

    XMLWordPrintable

    Details

    • Similar Issues:

      Description

      In our company we use the git-flow convention with feature and support branches. For all branches having a "/", e.g. "support/5.6.x" the test result page is not shown.

      The link to the test report seems fine and it contains: "https://.../job/support%252F5.6.x/1/testReport"
      but when clicking on the link, the following URL is visited: "https://.../job/support%2F5.6.x/1/testReport"

      By manually fixing the URL by adding "25", the test report is finally shown. However the detail links on the test page are still broken.

      I found a similar issue, but that one seemed to be fixed a long while ago: https://issues.jenkins-ci.org/browse/JENKINS-36154

        Attachments

          Activity

          Ascending order - Click to sort in descending order
          Hide
          Permalink
          kon Kalle Niemitalo added a comment -

          Where does the incorrect link appear; can you post the URL and HTML? We use Git branch names like "release/1.34" here and I don't see this problem.

          Do you run Jenkins behind an HTTP proxy that might decode the %25 escapes before Jenkins receives them?

          Show
          kon Kalle Niemitalo added a comment - Where does the incorrect link appear; can you post the URL and HTML? We use Git branch names like "release/1.34" here and I don't see this problem. Do you run Jenkins behind an HTTP proxy that might decode the %25 escapes before Jenkins receives them?
          Hide
          Permalink
          awallat André Wallat added a comment -

          Thank you very much for the hint! That brought me into the right direction.

          In my apache configuration I had to add the following line inside the VirtualHost definition:

          AllowEncodedSlashes NoDecode
          Show
          awallat André Wallat added a comment - Thank you very much for the hint! That brought me into the right direction. In my apache configuration I had to add the following line inside the VirtualHost definition: AllowEncodedSlashes NoDecode

            People

            Assignee:
            Unassigned Unassigned
            Reporter:
            awallat André Wallat
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved: