[JIRA] (JENKINS-53261) Blue ocean should handle non-encoded URLs for jobs in folders
Title: Message Title Euclid Sun edited a comment on JENKINS-53261 Re: Blue ocean should handle non-encoded URLs for jobs in folders A workaround is to create links that are appended with a / forcing the browser to not encode anything in the URL and read it as-is with no replacements. If we could have urls from the plugin show up automatically appended with / this would solve a large amount of issues so long as no one tries to post a link from the dashboard without the /However it is still a workaround from just being able to read a fix would be reading the folder names and reserving blue/organizations/jenkinsdetail\d+/pipelineas reserve words so that the labels for folders can be read in correctly regardless if they are replaced Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.193336.1535399409000.9315.1586569740343%40Atlassian.JIRA.
[JIRA] (JENKINS-53261) Blue ocean should handle non-encoded URLs for jobs in folders
Title: Message Title Euclid Sun edited a comment on JENKINS-53261 Re: Blue ocean should handle non-encoded URLs for jobs in folders A way around workaround is to create links that are appended with a / forcing the browser to not encode anything in the URL and read it as-is with no replacements. If we could have urls from the plugin show up automatically appended with / this would solve a large amount of issues so long as no one tries to post a link from the dashboard without the /However it is still a workaround from just being able to read the folder names and reserving blue/organizations/jenkinsdetail\d+/pipelineas reserve words so that the labels for folders can be read in correctly regardless if they are replaced Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.193336.1535399409000.9313.1586569740316%40Atlassian.JIRA.
[JIRA] (JENKINS-53261) Blue ocean should handle non-encoded URLs for jobs in folders
Title: Message Title Euclid Sun commented on JENKINS-53261 Re: Blue ocean should handle non-encoded URLs for jobs in folders A way around is to create links that are appended with a / forcing the browser to not encode anything in the URL and read it as-is with no replacements. If we could have urls from the plugin show up automatically appended with / this would solve a large amount of issues so long as no one tries to post a link from the dashboard without the / However it is still a workaround from just being able to read the folder names and reserving blue/organizations/jenkins detail \d+/pipeline as reserve words so that the labels for folders can be read in correctly regardless if they are replaced Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.193336.1535399409000.9305.1586569680190%40Atlassian.JIRA.
[JIRA] (JENKINS-53261) Blue ocean should handle non-encoded URLs for jobs in folders
Title: Message Title hboutemy commented on JENKINS-53261 Re: Blue ocean should handle non-encoded URLs for jobs in folders same issue here: following "Open Blue Ocean" link in the left menu of https://builds.apache.org/view/M-R/view/Maven/job/maven-box/job/maven/ brings me to "Page not found (404)" I'm using Firefox 65.0 and Chromium 71.0.3578.98 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53261) Blue ocean should handle non-encoded URLs for jobs in folders
Title: Message Title Robert Scholte commented on JENKINS-53261 Re: Blue ocean should handle non-encoded URLs for jobs in folders It looks like some browsers like Chrome think they are smart and they replace the %2F with a / making it an URL blue ocean doesn't expect. I kind of understand why Chrome might do this, but it doesn't help us here. Consider using a more safe separator (maybe configurable) Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53261) Blue ocean should handle non-encoded URLs for jobs in folders
Title: Message Title Brian Saville created an issue Jenkins / JENKINS-53261 Blue ocean should handle non-encoded URLs for jobs in folders Issue Type: Improvement Assignee: Unassigned Components: blueocean-plugin Created: 2018-08-27 19:50 Priority: Major Reporter: Brian Saville Two important points: 1) we're using jobs inside of folders, sometimes up to 4 levels deep, 2) we're sending links in email notifications to our users for failed builds, etc. As it turns out Outlook 365 has ATP (Active Threat Protection) which wraps URLs from "unknown" or not specifically whitelisted addresses in another site controlled by MS. I've confirmed using http://www.o365atp.com/ that the URL encoding for the full job path (i.e. /blue/organizations/jenkins/folder%2Fjob/detail/...) is correct in the wrapped link. Unfortunately, their ATP endpoints returns a 302 with a location that has been URL decoded one too many times, so that I end up with /blue/organizations/jenkins/folder/job/detail/...). This fails to load in blue ocean since it does not handle job paths with actual slashes instead of URL encoded slashes (%2F). Obviously the best answer is that MS should fix their stuff, but I don't think that's going to happen anytime soon. I can also workaround this by using nginx rewrites since we are behind nginx. However, those rewrites are messy and difficult to get right for arbitrary depths of folders. IMHO, blue ocean should be able to handle paths that are not URL encoded for jobs, since there are markers before and after the job (/jenkins/ and /detail/, etc). Is there a chance that we could improve the URL routing to handle this? I'm happy to take a look myself, but I'm not sure where the actual routing is being done for blue ocean.
