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

Jenkins cannot handle redirects from http to https URLs in update sites

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Minor Minor
    • core
    • None

      Jenkins does not handle redirects from HTTP to HTTPS URLs in update sites. So we cannot have HTTPS update sites, as all URLs in update-center.json are HTTP.

          [JENKINS-38340] Jenkins cannot handle redirects from http to https URLs in update sites

          Daniel Beck added a comment -

          Useful comments in JENKINS-8028.

          Daniel Beck added a comment - Useful comments in JENKINS-8028 .

          Daniel Beck added a comment -

          Related comments in JENKINS-32796 as well, but not adding anything new.

          Daniel Beck added a comment - Related comments in JENKINS-32796 as well, but not adding anything new.

          Daniel Beck added a comment -

          JENKINS-32796 and JENKINS-8028 are not actually related issues, but comments have been posted to those issues about this particular problem.

          Daniel Beck added a comment - JENKINS-32796 and JENKINS-8028 are not actually related issues, but comments have been posted to those issues about this particular problem.

          I currently ran into this issue becaue the maschine I want to install does not allow connections via http at all.

          So even if the urls redirect from http to https the proxy will refuse the connection.

          Is there any chance that the update-center.json will return urls in https when requesting the file via https?

          Benjamin Asbach added a comment - I currently ran into this issue becaue the maschine I want to install does not allow connections via http at all. So even if the urls redirect from http to https the proxy will refuse the connection. Is there any chance that the update-center.json will return urls in https when requesting the file via https?

          Daniel Beck added a comment -

          asbachb No, see INFRA-266 etc.

          Daniel Beck added a comment - asbachb No, see INFRA-266 etc.

          Mike Duigou added a comment -

          The osuosl mirrors no longer support http. Attempting to update plugins results in:

          java.io.IOException: Server returned HTTP response code: 503 for URL: http://ftp-chi.osuosl.org/pub/jenkins/plugins/subversion/2.9/subversion.hpi

          reattempting the same URL in a browser using https works fine.

          Mike Duigou added a comment - The osuosl mirrors no longer support http. Attempting to update plugins results in: java.io.IOException: Server returned HTTP response code: 503 for URL: http://ftp-chi.osuosl.org/pub/jenkins/plugins/subversion/2.9/subversion.hpi reattempting the same URL in a browser using https works fine.

          Christopher Orr added a comment - - edited

          bondolo: HTTP 503 is a temporary failure. That http:// URL from OSUOSL currently works fine for me. Do you have any sources mentioning that they are revoking http:// service?

          Christopher Orr added a comment - - edited bondolo : HTTP 503 is a temporary failure. That http:// URL from OSUOSL currently works fine for me. Do you have any sources mentioning that they are revoking http:// service?

          Daniel Beck added a comment -

          Link works for me too.

          Also, would be an infra issue, not a Jenkins issue.

          Daniel Beck added a comment - Link works for me too. Also, would be an infra issue, not a Jenkins issue.

          Mike Duigou added a comment -

          hmmm, working for me as well from a different network.

          The non-infra part of this issue would be that using an https update server should use https in the update results it provides. I was tempted to retrieve the update file, edit the urls with sed and then host that update file with the amended urls. Perhaps the urls in the update file should be absolute path only without protocol or host and resolved relative to the update url?

          Mike Duigou added a comment - hmmm, working for me as well from a different network. The non-infra part of this issue would be that using an https update server should use https in the update results it provides. I was tempted to retrieve the update file, edit the urls with sed and then host that update file with the amended urls. Perhaps the urls in the update file should be absolute path only without protocol or host and resolved relative to the update url?

          bondolo: That's not possible as the download URLs redirect to various mirrors outside of our control, so we can't do anything unless they all provide https:// access all the time; see INFRA-266.

          Christopher Orr added a comment - bondolo : That's not possible as the download URLs redirect to various mirrors outside of our control, so we can't do anything unless they all provide https:// access all the time; see INFRA-266.

            fcojfernandez Francisco Fernández
            tedwang wang ted
            Votes:
            6 Vote for this issue
            Watchers:
            9 Start watching this issue

              Created:
              Updated: