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

Try to access to a private URL returns a 404 instead of a 401

    XMLWordPrintable

Details

    • Bug
    • Status: Resolved (View Workflow)
    • Major
    • Resolution: Fixed
    • core
    • None
    • hudson 1.387 + Apache/modjk

    Description

      This problem exists for a very long time and even if it isn't blocker it is annoying.
      You can easily reproduce it by creating a job in an hudson instance (using the security matrix) and you don't give access to it to anonymous.
      Logout and try to access to the project URL

      This is annoying because teams are receiving emails from hudson saying to have a look at the url of the build failure and they are faced to a 404 ...

      A 501 error (with the login page ?) should be really better in term of ergonomics

      Attachments

        Issue Links

          Activity

            aheritier Arnaud Héritier created issue -
            ohtake_tomohiro OHTAKE Tomohiro made changes -
            Field Original Value New Value
            Link This issue is related to JENKINS-4740 [ JENKINS-4740 ]
            abayer Andrew Bayer made changes -
            Link This issue is duplicated by JENKINS-10869 [ JENKINS-10869 ]
            scm_issue_link SCM/JIRA link daemon made changes -
            Resolution Fixed [ 1 ]
            Status Open [ 1 ] Resolved [ 5 ]
            aheritier Arnaud Héritier made changes -
            Link This issue is blocking JENKINS-13999 [ JENKINS-13999 ]
            rtyler R. Tyler Croy made changes -
            Workflow JNJira [ 138318 ] JNJira + In-Review [ 187950 ]

            People

              Unassigned Unassigned
              aheritier Arnaud Héritier
              Votes:
              9 Vote for this issue
              Watchers:
              8 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: