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

Invalid URL containing port

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Resolved (View Workflow)
    • Priority: Blocker
    • Resolution: Fixed
    • Component/s: core
    • Labels:
    • Environment:
      Jenkins 2.261 and 2.262
    • Similar Issues:
    • Released As:
      Jenkins 2.263

      Description

      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.

       

        Attachments

          Issue Links

          is duplicated by

          Bug - A problem which impairs or prevents the functions of the product. JENKINS-63961 Reverse proxy set up is broken on Windows, as a service, with no IIS or other reverse proxy

          • Critical - Crashes, loss of data, severe memory leak.
          • Closed
          relates to

          Improvement - An improvement or enhancement to an existing feature or task. JENKINS-64035 Upgrade Jetty to 9.4.33

          • Major - Major loss of function.
          • Resolved
          links to

          Web Link https://github.com/jenkinsci/jenkins/pull/5017

            Activity

            Ascending order - Click to sort in descending order
            19 older comments
            Hide
            Permalink
            oleg_nenashev Oleg Nenashev added a comment -

            https://github.com/jenkinsci/jenkins/pull/5017 as a last resort rollback fix. Taking the confirmation by Richard Fearn, I believe our best option is to pick up the Jetty release which is expected soon. If it does not happen tomorrow until the weekly release, we might cut another out of order weekly release once new Jetty is available.

             

            It worth mentioning that yet another Jetty upgrade would increase risk of additional reressions in the weekly. Also, it might be impediment for the LTS baseline selection which is expected to happen this week.

             

            Show
            oleg_nenashev Oleg Nenashev added a comment - https://github.com/jenkinsci/jenkins/pull/5017  as a last resort rollback fix. Taking the confirmation by Richard Fearn , I believe our best option is to pick up the Jetty release which is expected soon. If it does not happen tomorrow until the weekly release, we might cut another out of order weekly release once new Jetty is available.   It worth mentioning that yet another Jetty upgrade would increase risk of additional reressions in the weekly. Also, it might be impediment for the LTS baseline selection which is expected to happen this week.  
            Hide
            Permalink
            richardfearn Richard Fearn added a comment -

            Everything seems to be working fine again with 2.263. Thanks to everyone who has worked on this

            Show
            richardfearn Richard Fearn added a comment - Everything seems to be working fine again with 2.263. Thanks to everyone who has worked on this
            Hide
            Permalink
            fabiang Fabian Grutschus added a comment -

            Can confirm it's working again.

            Show
            fabiang Fabian Grutschus added a comment - Can confirm it's working again.
            Hide
            Permalink
            bcoveny Bruce Coveny added a comment -

            Also confirming that 2.263 is back to functioning as expected. Thanks Oleg Nenashev! 

            Show
            bcoveny Bruce Coveny added a comment - Also confirming that 2.263 is back to functioning as expected. Thanks Oleg Nenashev ! 
            Hide
            Permalink
            oleg_nenashev Oleg Nenashev added a comment -

            Marking it as resolved based on the feedback. Thanks all!

            Show
            oleg_nenashev Oleg Nenashev added a comment - Marking it as resolved based on the feedback. Thanks all!

              People

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

                Dates

                Created:
                Updated:
                Resolved: