[JENKINS-73384] 404 Page Not Found - on refresh of pipeline page which is within folder

[jenkins-infra-bot]

We have upgraded to latest blue ocean plugin (1.27.13) and experiencing 404 page not found error on refreshing of any pipeline page.

 

We observed that the URL loaded by blue ocean is having URL encoded value of path separator %2F instead of forward slash / in URLs.

 

This is the URL that's displayed on opening pipeline page in blue ocean: https://<>/blue/organizations/jenkins/Others%2FINFRA_TEST_PIPELINES%2FInfra_test/activity

and this URL works!

 

It can be seen that the path separator value is %2F instead of / and page loads perfectly.

On page refresh the %2F is getting replaced with / automatically and we are getting 404 page not found error.

 

---

Originally reported by jeninjames, imported from: 404 Page Not Found - on refresh of pipeline page which is within folder

• status: In Progress
• priority: Minor
• component(s): blueocean-plugin
• label(s): blueocean, plugin
• resolution: Unresolved
• votes: 1
• watchers: 4
• imported: 2025-12-01

Raw content of original issue

We have upgraded to latest blue ocean plugin (1.27.13) and experiencing 404 page not found error on refreshing of any pipeline page.

 

We observed that the URL loaded by blue ocean is having URL encoded value of path separator %2F instead of forward slash / in URLs.

 

This is the URL that's displayed on opening pipeline page in blue ocean: https://<<domain>>/blue/organizations/jenkins/Others%2FINFRA_TEST_PIPELINES%2FInfra_test/activity

and this URL works!



 

It can be seen that the path separator value is %2F instead of / and page loads perfectly.

On page refresh the %2F is getting replaced with / automatically and we are getting 404 page not found error.



 

5 attachments

• Jenkins 2.464 - new url.png

  

• Jenkins 2.464 - old url (getting changed during auto reload).png

  

• image-2024-07-02-18-13-09-982.png

  

• image-2024-07-02-18-14-09-249.png

  

• image-2025-10-06-15-33-08-961.png

  

[jenkins-infra-bot]

mahender_nirwan:

• Original comment link
• Raw content of original comment:

  jeninjames This issue is because the proxy is not allowing urls with encoded slashed to go through.
  
  I fixed this issue by adding AllowEncodedSlashes NoDecode property in .conf file of apache proxy.
  Please go through the documentation here for you respect proxy type.
  
  

jeninjames This issue is because the proxy is not allowing urls with encoded slashed to go through.

I fixed this issue by adding AllowEncodedSlashes NoDecode property in .conf file of apache proxy.
Please go through the documentation here for you respect proxy type.

[jenkins-infra-bot]

mihai_p1234:

• Original comment link
• Raw content of original comment:

  Hi,
  
  In our case even with AllowEncodedSlashes NoDecode still doesn't work : opening Blue Ocean from the Jenkins main page, searching for a job show results at first but after a refresh gives 400.  And the second issues is the fact that URL gives 400 when going into a job and trying to open Blue Ocean from there. 
  
  Using the latest 1.27.16 version
  

Hi,

In our case even with AllowEncodedSlashes NoDecode still doesn't work : opening Blue Ocean from the Jenkins main page, searching for a job show results at first but after a refresh gives 400.  And the second issues is the fact that URL gives 400 when going into a job and trying to open Blue Ocean from there. 

Using the latest 1.27.16 version

[jenkins-infra-bot]

ilyess_mez78:

• Original comment link
• Raw content of original comment:

  Hi we're facing same issue when clicking on blue ocean button on build sidebar  : 
  
  
  
  FYI, jenkins is deployed on EKS behind an nginx ingress controller , controller version 2.523 , Blue Ocean plugin 1.27.21 . 
  
  
   
  

Hi we're facing same issue when clicking on blue ocean button on build sidebar  : 

FYI, jenkins is deployed on EKS behind an nginx ingress controller , controller version 2.523 , Blue Ocean plugin 1.27.21 .