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

blue ocean URL redirection converting %2F to %252F%

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Minor Minor
    • blueocean-plugin
    • None

      Clicking Job changes through blue ocen shows "Page not found"

      The URL is converting %2F% to %252F%.

      https://<HOST>/blue/organizations/<JOB URL>/changes

          [JENKINS-47604] blue ocean URL redirection converting %2F to %252F%

          James Dumay added a comment -

          I believe this has been fixed and released as part of JENKINS-47073. Please reopen if that is not the case.

          James Dumay added a comment - I believe this has been fixed and released as part of JENKINS-47073 . Please reopen if that is not the case.

          I believe JENKINS-47535 resolved this issue for multi-branch  Git repositories, but it is still an issue for anything else that has a forward slash in its display name. If you have a pipeline that is a job with children, then the pipeline for one of the youngest generations of children will have a display name with forward slashes showing the hierarchy. This is converted to %2F for URLs, but afterwards it is rewritten again to %252F.

          Please contact me if you need more information.

          Nicholas Geyer added a comment - I believe JENKINS-47535 resolved this issue for multi-branch  Git repositories, but it is still an issue for anything else that has a forward slash in its display name. If you have a pipeline that is a job with children, then the pipeline for one of the youngest generations of children will have a display name with forward slashes showing the hierarchy. This is converted to %2F for URLs, but afterwards it is rewritten again to %252F. Please contact me if you need more information.

          Still very much happens, and breaks use of blue ocean for any job in a folder. Even when manually repairing the URL to reach the correct page, any Refresh on that page re-breaks it.

          Tim Van Holder added a comment - Still very much happens, and breaks use of blue ocean for any job in a folder. Even when manually repairing the URL to reach the correct page, any Refresh on that page re-breaks it.

          Facundo Mateo added a comment -

          Same problem with  Folder organizations on  blue ocean.  

          For us this made blueocean  unusable. We have decided to use the classic jenkins view instead.

          Facundo Mateo added a comment - Same problem with  Folder organizations on  blue ocean.   For us this made blueocean  unusable. We have decided to use the classic jenkins view instead.

          Jule added a comment -

          2023 and BO still completely unusable due to this easy-to-fix bug...

          Jule added a comment - 2023 and BO still completely unusable due to this easy-to-fix bug...

          jin hur added a comment -

          I believe I have the same problem.
          For me, I'm using Multibranch configuration and the problematic branch name is "release/v3.21.192.0".
          If I visit my branch page like below, Blue Ocean page shows successfully.
          1. Load http://my-jenkins/jenkins/job/my-build/
          2. Hit "release/v3.21.192.0"
          2. Hit "Open Blue Ocean"
          3. Hit "release/v3.21.192.0"
          4. BO page for release/v3.21.192.0 branch is loaded successfully. 
             Current URL is https://my-jenkins/jenkins/blue/organizations/jenkins/my-build/detail/release%2Fv3.21.192.0/36/pipeline 

          But when I refresh the page. 400 bad request response is received.
          If I replace %2F with / on my web browser, then the page is redirected to "https://my-jenkins/jenkins/blue/organizations/jenkins/my-build/detail/release%2Fv3.21.192.0/36/pipeline/".
          (Please note that a trailing forward slash is added)

          But at this time, the response is 403 Forbidden.
          It seems this is because JSESSIONID cookie is missing in the redirection request.

          I've been going through this problem for a long time.
          It would be great if this problem can be solved soon or anyone can tell me any workaround.

          jin hur added a comment - I believe I have the same problem. For me, I'm using Multibranch configuration and the problematic branch name is "release/v3.21.192.0". If I visit my branch page like below, Blue Ocean page shows successfully. 1. Load http://my-jenkins/jenkins/job/my-build/ 2. Hit "release/v3.21.192.0" 2. Hit "Open Blue Ocean" 3. Hit "release/v3.21.192.0" 4. BO page for release/v3.21.192.0 branch is loaded successfully.     Current URL is https://my-jenkins/jenkins/blue/organizations/jenkins/my-build/detail/release%2Fv3.21.192.0/36/pipeline   But when I refresh the page. 400 bad request response is received. If I replace %2F with / on my web browser, then the page is redirected to "https://my-jenkins/jenkins/blue/organizations/jenkins/my-build/detail/release%2Fv3.21.192.0/36/pipeline/". (Please note that a trailing forward slash is added) But at this time, the response is 403 Forbidden. It seems this is because JSESSIONID cookie is missing in the redirection request. I've been going through this problem for a long time. It would be great if this problem can be solved soon or anyone can tell me any workaround.

            jamesdumay James Dumay
            gthiyaga GOGULAKRISHNAN THIYAGARAJAN
            Votes:
            7 Vote for this issue
            Watchers:
            12 Start watching this issue

              Created:
              Updated: