• Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Blocker Blocker
    • core
    • Jenkins 2.261 and 2.262
    • Jenkins 2.263

      Updating to 2.261 and even 2.262 the URL for some links are injecting the port number ":80" which in our instance is invalid.  This prevents pages from loading. For example the "search" at top of screen when finding a job and trying to go to the job will change the URL from "https://jenkins.company.com/" to "https://jenkins.company.com:80/job/jobname/".  This makes pages not render properly and user needs to remove ":80" from URL to continue.

      Another instance is clicking Manage Jenkins -> Manage Plugins goes from "https://jenkins.company.com/manage" to "https://jenkins.company.com:80/pluginManager/".

      These are just a couple of instances but have run into more.  I couldn't easily identity what change in 2.261 that affected this behavior.

       

          [JENKINS-63958] Invalid URL containing port

          Bruce Coveny created issue -
          Bruce Coveny made changes -
          Description Original: Updating to 2.261 and even 2.262 the URL for some links are injecting the port number ":80" which in our instance is invalid.  This prevents pages from loading. For example the "search" at top of screen when finding a job and trying to go to the job will change the URL from "https://jenkins.company.com/" to "https://jenkins.company.com:80/job/jobname/".  This makes pages not render properly and user needs to remove ":80" from URL to continue.

           

          Another instance is clicking Manage Jenkins -> Manage Plugins goes from "https://jenkins.company.com/manage" to "https://jenkins.company.com:80/pluginManager/".


          These are just a couple of instances but have run into more.  I couldn't easily identity what change in 2.261 that affected this behavior.

           
          New: Updating to 2.261 and even 2.262 the URL for some links are injecting the port number ":80" which in our instance is invalid.  This prevents pages from loading. For example the "search" at top of screen when finding a job and trying to go to the job will change the URL from "https://jenkins.company.com/" to "https://jenkins.company.com:80/job/jobname/".  This makes pages not render properly and user needs to remove ":80" from URL to continue.

          Another instance is clicking Manage Jenkins -> Manage Plugins goes from "https://jenkins.company.com/manage" to "https://jenkins.company.com:80/pluginManager/".

          These are just a couple of instances but have run into more.  I couldn't easily identity what change in 2.261 that affected this behavior.

           

          Oleg Nenashev added a comment -

          bcoveny what Jenkins version did you use before the upgrade?

          Oleg Nenashev added a comment - bcoveny what Jenkins version did you use before the upgrade?

          Bruce Coveny added a comment -

          oleg_nenashev we were using 2.260 which is where I know it was a change in 2.261 which caused the issue.  We have 3 other instances running...2 with 2.260 and 1 with 2.258. 

          Bruce Coveny added a comment - oleg_nenashev we were using 2.260 which is where I know it was a change in 2.261 which caused the issue.  We have 3 other instances running...2 with 2.260 and 1 with 2.258. 

          Oleg Nenashev added a comment -

          Could it be somehow related to the Jetty upgrade olamy? I do not see anything else which would be immediately suspicious

          bcoveny could you please confirm that you are using the embedded Jetty web server?

          Oleg Nenashev added a comment - Could it be somehow related to the Jetty upgrade olamy ? I do not see anything else which would be immediately suspicious bcoveny could you please confirm that you are using the embedded Jetty web server?
          Oleg Nenashev made changes -
          Labels New: regression

          Olivier Lamy added a comment -

          sound possible but I'm not sure how the url is injected (different injection in different places)

          Olivier Lamy added a comment - sound possible but I'm not sure how the url is injected (different injection in different places)

          Zbynek Konecny added a comment - - edited

          I can confirm this happens on Jenkins installed via debian package, running without any proxy on HTTPS port 443. No problem with 2.260. The process is started like this

           /usr/bin/java -Dhudson.DNSMultiCast.disabled=true -Djava.awt.headless=true -jar /usr/share/jenkins/jenkins.war --webroot=/var/cache/jenkins/war --httpsPort=443 --ajp13Port=-1 --httpsCertificate=/foo/bar.pem --httpsPrivateKey=/foo/bar.key 

          Also the "reverse proxy broken" administrative monitor became active. Since this was a production Jenkins install I had to roll back to 260, but if more info is needed I can check again.

          Zbynek Konecny added a comment - - edited I can confirm this happens on Jenkins installed via debian package, running without any proxy on HTTPS port 443. No problem with 2.260. The process is started like this /usr/bin/java -Dhudson.DNSMultiCast.disabled= true -Djava.awt.headless= true -jar /usr/share/jenkins/jenkins.war --webroot=/ var /cache/jenkins/war --httpsPort=443 --ajp13Port=-1 --httpsCertificate=/foo/bar.pem --httpsPrivateKey=/foo/bar.key Also the "reverse proxy broken" administrative monitor became active. Since this was a production Jenkins install I had to roll back to 260, but if more info is needed I can check again.

          Olivier Lamy added a comment -

          something not clear. Are you guys using proxy? how is it configured?

          Olivier Lamy added a comment - something not clear. Are you guys using proxy? how is it configured?

          Richard Fearn added a comment - - edited

          Same issue here. 2.260 was fine; 2.261 has this problem. I have Jenkins running on port 8443 with an iptables redirect from 443 to 8443. So I always access the instance using https://mydomain/ and the "Jenkins URL" in the settings is also set to "https://mydomain/".

          One place where the problem occurs is enabling/disabling a project - clicking the Enable/Disable button loads https://mydomain:80/job/JOBNAME/. The project does get enabled/disabled, but the redirect to that URL (including ":80") is wrong.

          Richard Fearn added a comment - - edited Same issue here. 2.260 was fine; 2.261 has this problem. I have Jenkins running on port 8443 with an iptables redirect from 443 to 8443. So I always access the instance using https://mydomain/ and the "Jenkins URL" in the settings is also set to "https://mydomain/". One place where the problem occurs is enabling/disabling a project - clicking the Enable/Disable button loads https://mydomain:80/job/JOBNAME/ . The project does get enabled/disabled, but the redirect to that URL (including ":80") is wrong.

            Unassigned Unassigned
            bcoveny Bruce Coveny
            Votes:
            4 Vote for this issue
            Watchers:
            13 Start watching this issue

              Created:
              Updated:
              Resolved: