Since upgrading from Jenkins 1.552 to 1.556 I see the following error when I attempt to login to Jenkins:

      HTTP ERROR 404
      Problem accessing /jenkins/;jsessionid=1vdumbbfrnzw1ikx0jl5mqi6q. Reason:

      Not Found

      I can successfully login by deleting the Jenkins cookie in my browser (IE9) but the problem reoccurs later.

      I am using the latest ActiveDirectory plugin.

          [JENKINS-22358] Jenkins 1.556 gives 'Error 404 Not Found'

          Manni added a comment -

          I have a feeling that this is triggered when the jenkins url contains a port number.

          I just tried accessing my jenkins instance through a SSH tunnel (something that used to work until we upgraded to 1.583) and promptly ran into the problem. Logging in using our normal, intra-net, URL works just fine.

          HTTP/1.1 302 Found
          Set-Cookie: JSESSIONID.3a3afa59=1osdlnih6c42p1kkmc0uhgrmmz;Path=/tools/jenkins;Secure;HttpOnly
          Expires: Thu, 01 Jan 1970 00:00:00 GMT
          Location: http://127.0.0.2:8080/tools/jenkins/;jsessionid=1osdlnih6c42p1kkmc0uhgrmmz
          Content-Length: 0
          Server: Jetty(8.y.z-SNAPSHOT)
          

          Manni added a comment - I have a feeling that this is triggered when the jenkins url contains a port number. I just tried accessing my jenkins instance through a SSH tunnel (something that used to work until we upgraded to 1.583) and promptly ran into the problem. Logging in using our normal, intra-net, URL works just fine. HTTP/1.1 302 Found Set-Cookie: JSESSIONID.3a3afa59=1osdlnih6c42p1kkmc0uhgrmmz;Path=/tools/jenkins;Secure;HttpOnly Expires: Thu, 01 Jan 1970 00:00:00 GMT Location: http: //127.0.0.2:8080/tools/jenkins/;jsessionid=1osdlnih6c42p1kkmc0uhgrmmz Content-Length: 0 Server: Jetty(8.y.z-SNAPSHOT)

          Code changed in jenkins
          User: Kohsuke Kawaguchi
          Path:
          changelog.html
          war/pom.xml
          http://jenkins-ci.org/commit/jenkins/3addbabf8afae39022440d63216a360233dabc80
          Log:
          [FIXED JENKINS-22358]

          Integrated the newer version of Winstone

          SCM/JIRA link daemon added a comment - Code changed in jenkins User: Kohsuke Kawaguchi Path: changelog.html war/pom.xml http://jenkins-ci.org/commit/jenkins/3addbabf8afae39022440d63216a360233dabc80 Log: [FIXED JENKINS-22358] Integrated the newer version of Winstone

          dogfood added a comment -

          Integrated in jenkins_main_trunk #3737
          [FIXED JENKINS-22358] (Revision 3addbabf8afae39022440d63216a360233dabc80)

          Result = SUCCESS
          kohsuke : 3addbabf8afae39022440d63216a360233dabc80
          Files :

          • war/pom.xml
          • changelog.html

          dogfood added a comment - Integrated in jenkins_main_trunk #3737 [FIXED JENKINS-22358] (Revision 3addbabf8afae39022440d63216a360233dabc80) Result = SUCCESS kohsuke : 3addbabf8afae39022440d63216a360233dabc80 Files : war/pom.xml changelog.html

          Daniel Beck added a comment -

          Having a port is the default, so it should occur much more often if that alone were the reason.

          Daniel Beck added a comment - Having a port is the default, so it should occur much more often if that alone were the reason.

          Damien Nozay added a comment -

          It may be related to https://github.com/jenkinsci/jenkins/commit/79c905e6d0b03b075eef5339b73a6e8c55acd620

          If you logged in with https:// and had a cookie with secure flag
          then if you visit the same link with http:// instead, you cannot use the cookie.

          Damien Nozay added a comment - It may be related to https://github.com/jenkinsci/jenkins/commit/79c905e6d0b03b075eef5339b73a6e8c55acd620 If you logged in with https:// and had a cookie with secure flag then if you visit the same link with http:// instead, you cannot use the cookie.

          Liam Reimers added a comment -

          Damien: That jives - I see that the 404 is an http: page, and when I replace that with https: (and remove the jsessionid cruft) it works as expected.

          Liam Reimers added a comment - Damien: That jives - I see that the 404 is an http: page, and when I replace that with https: (and remove the jsessionid cruft) it works as expected.

          John Barnes added a comment -

          This issue seems to have reappeared. We're using v.1.626 and have also reproduced this issue with the latest LTS 1.609.2 as well.

          Behavior:
          1. Login with valid credentials,
          2. 404 "Not found" page displays,
          3. Remove session ID URL parameter and hit enter,
          4. Jenkins home displays for the credentialed user.

          This behavior is the same whether we invoke Jenkins through our Nginx reverse proxy (http://192.168.41.1/jenkins) or bypass the proxy and go directly to Jenkins running on http://192.168.41.1:8080/jenkins.

          Environment:
          AWS Ubuntu 14.04 EC2 instance
          VPN access only (192.168.41.1 Nat'd to the instance's private IP)
          Jenkins 1.626
          WildFly 9.0.1.Final
          Nginx 1.4.6 (on port 80 with reverse proxy to Jenkins running on WildFly 8080)
          Oracle Java build 1.8.0_60-b27

          John Barnes added a comment - This issue seems to have reappeared. We're using v.1.626 and have also reproduced this issue with the latest LTS 1.609.2 as well. Behavior: 1. Login with valid credentials, 2. 404 "Not found" page displays, 3. Remove session ID URL parameter and hit enter, 4. Jenkins home displays for the credentialed user. This behavior is the same whether we invoke Jenkins through our Nginx reverse proxy ( http://192.168.41.1/jenkins ) or bypass the proxy and go directly to Jenkins running on http://192.168.41.1:8080/jenkins . Environment: AWS Ubuntu 14.04 EC2 instance VPN access only (192.168.41.1 Nat'd to the instance's private IP) Jenkins 1.626 WildFly 9.0.1.Final Nginx 1.4.6 (on port 80 with reverse proxy to Jenkins running on WildFly 8080) Oracle Java build 1.8.0_60-b27

          This happens also on JBoss EAP7 as htpps sessions in URL are enabled by default.
          I submitted a pull request to disable the jsessionid in deployments of Jenkins on jboss.

          https://github.com/jenkinsci/jenkins/pull/2003

          Francesco Pagetti added a comment - This happens also on JBoss EAP7 as htpps sessions in URL are enabled by default. I submitted a pull request to disable the jsessionid in deployments of Jenkins on jboss. https://github.com/jenkinsci/jenkins/pull/2003

          Oleg Nenashev added a comment -

          Added a link to https://issues.jboss.org/browse/WFLY-4782 with extra details

          Oleg Nenashev added a comment - Added a link to https://issues.jboss.org/browse/WFLY-4782 with extra details

          Code changed in jenkins
          User: pagio81
          Path:
          war/src/main/webapp/WEB-INF/jboss-web.xml
          http://jenkins-ci.org/commit/jenkins/2f6b3d581617438a6efe0b910989ddaa9669eaa3
          Log:
          JENKINS-22358 - Disable JSESSIONID in URL on JBoss (#2003)

          More details: https://issues.jboss.org/browse/WFLY-4782

          SCM/JIRA link daemon added a comment - Code changed in jenkins User: pagio81 Path: war/src/main/webapp/WEB-INF/jboss-web.xml http://jenkins-ci.org/commit/jenkins/2f6b3d581617438a6efe0b910989ddaa9669eaa3 Log: JENKINS-22358 - Disable JSESSIONID in URL on JBoss (#2003) More details: https://issues.jboss.org/browse/WFLY-4782

            Unassigned Unassigned
            davida2009 David Aldrich
            Votes:
            6 Vote for this issue
            Watchers:
            18 Start watching this issue

              Created:
              Updated: