• Icon: Bug Bug
    • Resolution: Not A Defect
    • Icon: Major Major
    • core
    • None
    • Windows 2008 R2, Apache 2.2, Jenkins 1.554.2

      I have Jenkins running behind Apache 2.2 reverse proxy in one box on a Windows Server 2008 R2. After upgrading Jenkins from 1.554.1 to 1.554.2. I got message "It appears that your reverse proxy set up is broken." in Manage Jenkins page. If I downgrade back to 1.554.1, problem is gone. I use SSL at front-end. However, Chrome Web developer Tool shows 1.554.2 Jenkins generated redirect pages in HTTP, not HTTPS.

          [JENKINS-23280] Version 1.554.2 broke reverse proxy

          Daniel Beck added a comment -

          Did you test whether that message also appears in 1.554.2 without hiding Jenkins behind a reverse proxy, or why do you claim that?

          What's the URL configured in Manage Jenkins » Configure System? HTTP or HTTPS? What happens when you change it?

          Is your reverse proxy setting the X-Forwarded-Proto header?

          Daniel Beck added a comment - Did you test whether that message also appears in 1.554.2 without hiding Jenkins behind a reverse proxy, or why do you claim that? What's the URL configured in Manage Jenkins » Configure System? HTTP or HTTPS? What happens when you change it? Is your reverse proxy setting the X-Forwarded-Proto header?

          Fred Wen added a comment -

          The message doesn't appear if Jenkins is not behind r-proxy.
          Setting X-Forwarded-Proto fixed the problem.

          Fred Wen added a comment - The message doesn't appear if Jenkins is not behind r-proxy. Setting X-Forwarded-Proto fixed the problem.

          Daniel Beck added a comment -

          Configuration issue.

          I documented this in the wiki, if you have anything to add, feel free to do so.

          Daniel Beck added a comment - Configuration issue. I documented this in the wiki , if you have anything to add, feel free to do so.

          Hi Daniel,

          this might work for mod_proxy, but we still encounter the problem while using mod_jk!

          And I really don't know what to do. The AllowEncodedSlashes NoDecode option was already set.

          Can you please tell me what to do if I want to use mod_jk (with https)?

          Best regards,
          René

          René Charbonneau added a comment - Hi Daniel, this might work for mod_proxy, but we still encounter the problem while using mod_jk! And I really don't know what to do. The AllowEncodedSlashes NoDecode option was already set. Can you please tell me what to do if I want to use mod_jk (with https)? Best regards, René

          Daniel Beck added a comment -

          Rene: Jira is an issue tracker, not a support site. Please direct questions to the jenkinsci-users list, or #jenkins on Freenode.

          That said, https://wiki.jenkins-ci.org/display/JENKINS/Tomcat may be relevant to you.

          Daniel Beck added a comment - Rene: Jira is an issue tracker, not a support site. Please direct questions to the jenkinsci-users list, or #jenkins on Freenode. That said, https://wiki.jenkins-ci.org/display/JENKINS/Tomcat may be relevant to you.

            Unassigned Unassigned
            fredwen Fred Wen
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: