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

Direct links to project page leads to 404 errors

    • Icon: Bug Bug
    • Resolution: Won't Fix
    • Icon: Major Major
    • core
    • None
    • 64-bit Windows.

      If I try to access a build's status page that I haven't seen in a while from its url (e.g., http://myserver:8080/job/Project/431/) I'll get the following error:

      Status Code: 404
      Exception:
      Stacktrace:
      (none)
      Generated by Winstone Servlet Engine v0.9.10 at Tue Mar 26 17:45:26 EDT 2013

      However if I navigate to the build from http://myserver:8080/job/Project everything works. It's actually enough to first load the project page and then everything that showed up in the "build history" will be accessible through direct links (I usually end up using the links when sending out build failure emails).

      It's maybe worth mentioning that I currently have ~800 builds.
      Jenkins.err and jenkins.out doesn't contain any information regarding the 404.

      I'm using matrix-based security where Anonymous can Read everything.

          [JENKINS-17374] Direct links to project page leads to 404 errors

          Simon Edwardsson created issue -
          Simon Edwardsson made changes -
          Component/s New: core [ 15593 ]
          Component/s Original: status-view [ 15728 ]
          Description Original: If I try to access a build's status page that I haven't seen in a while from its url (e.g., http://myserver:8080/job/Project/431/) I'll get the following error:

          Status Code: 404
          Exception:
          Stacktrace:
          (none)
          Generated by Winstone Servlet Engine v0.9.10 at Tue Mar 26 17:45:26 EDT 2013

          However if I navigate to the build from http://myserver:8080/job/Project everything works. It's actually enough just to load the project page first and then everything that showed up in the "build history" will be accessible through direct links (I usually end up using the links when sending out build failure emails).

          It's maybe worth mentioning that I currently have ~800 builds.
          When checking jenkins.err and jenkins.out doesn't contain any information regarding the 404.

          I'm using matrix-based security where Anonymous can Read everything.
          New: If I try to access a build's status page that I haven't seen in a while from its url (e.g., http://myserver:8080/job/Project/431/) I'll get the following error:

          Status Code: 404
          Exception:
          Stacktrace:
          (none)
          Generated by Winstone Servlet Engine v0.9.10 at Tue Mar 26 17:45:26 EDT 2013

          However if I navigate to the build from http://myserver:8080/job/Project everything works. It's actually enough to first load the project page and then everything that showed up in the "build history" will be accessible through direct links (I usually end up using the links when sending out build failure emails).

          It's maybe worth mentioning that I currently have ~800 builds.
          Jenkins.err and jenkins.out doesn't contain any information regarding the 404.

          I'm using matrix-based security where Anonymous can Read everything.
          Priority Original: Minor [ 4 ] New: Major [ 3 ]

          Hi all,

          Here we have exactly the same issue. Once we have accessed the "project summary page" everything is ok.

          We are running jenkins 1.526 on a windows xp 32bit and we have the ldap authentication enabled and the "connected user can do anything" option ticked.

          Idem, nothing in the logs. I have created a new logger with the finest level for all the classes but there is nothing relevant that I can found in it.

          Mathieu POUSSE added a comment - Hi all, Here we have exactly the same issue. Once we have accessed the "project summary page" everything is ok. We are running jenkins 1.526 on a windows xp 32bit and we have the ldap authentication enabled and the "connected user can do anything" option ticked. Idem, nothing in the logs. I have created a new logger with the finest level for all the classes but there is nothing relevant that I can found in it.
          Mathieu POUSSE made changes -
          Status Original: Open [ 1 ] New: In Progress [ 3 ]

          This isn't a bug but intentional behavior to prevent anonymous to know URL is a valid job name. Enable DISCOVER permission if you wish anonymous to be redirected to login.

          Nicolas De Loof added a comment - This isn't a bug but intentional behavior to prevent anonymous to know URL is a valid job name. Enable DISCOVER permission if you wish anonymous to be redirected to login.
          Nicolas De Loof made changes -
          Assignee New: Nicolas De Loof [ ndeloof ]
          Resolution New: Won't Fix [ 2 ]
          Status Original: In Progress [ 3 ] New: Closed [ 6 ]

          This happens even though I have the following enabled for Anonymous:
          Overall (Read), Job(Read, Discover), View (Read).

          Simon Edwardsson added a comment - This happens even though I have the following enabled for Anonymous: Overall (Read), Job(Read, Discover), View (Read).

          @ndeloof: I'm having the same issue, and we are using "Logged-in users can do anything". How can I enable the discover permission for anonymous users in this configuration?

          Thanks!

          Marnix Klooster added a comment - @ ndeloof : I'm having the same issue, and we are using "Logged-in users can do anything". How can I enable the discover permission for anonymous users in this configuration? Thanks!

          The issue reported here may be a duplicate of JENKINS-19418, which I'm having with 1.509.3 (LTS) and which is scheduled to be fixed in 1.509.4.

          Marnix Klooster added a comment - The issue reported here may be a duplicate of JENKINS-19418 , which I'm having with 1.509.3 (LTS) and which is scheduled to be fixed in 1.509.4.

          Code changed in jenkins
          User: Daniel Beck
          Path:
          core/src/main/java/hudson/model/Api.java
          http://jenkins-ci.org/commit/jenkins/0a241aafdbdf3ad15d34efa3077658c5770b9195
          Log:
          [JENKINS-17374 JENKINS-18116] Don't set gzip header for error

          SCM/JIRA link daemon added a comment - Code changed in jenkins User: Daniel Beck Path: core/src/main/java/hudson/model/Api.java http://jenkins-ci.org/commit/jenkins/0a241aafdbdf3ad15d34efa3077658c5770b9195 Log: [JENKINS-17374 JENKINS-18116] Don't set gzip header for error

            ndeloof Nicolas De Loof
            simedw Simon Edwardsson
            Votes:
            3 Vote for this issue
            Watchers:
            8 Start watching this issue

              Created:
              Updated:
              Resolved: