[
https://issues.jenkins-ci.org/browse/JENKINS-8214?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=161972#comment-161972
]
SCM/JIRA link daemon commented on JENKINS-8214:
-----------------------------------------------
Code changed in jenkins
User: Jerome Lacoste
Path:
changelog.html
core/src/main/java/hudson/model/Item.java
core/src/main/java/jenkins/model/Jenkins.java
core/src/main/resources/hudson/model/Messages.properties
http://jenkins-ci.org/commit/jenkins/3c349c0cd460bea2f017b52e92550bab0f91247e
Log:
Merge pull request #453 from
lacostej/lacostej-JENKINS-8214-access-private-URL-2
[FIXED JENKINS-8214] Added a DISCOVER permission to allow anonymous users to be
presented the login screen when accessing job URLs
Compare: https://github.com/jenkinsci/jenkins/compare/5f92a03...3c349c0
> Try to access to a private URL returns a 404 instead of a 401
> -------------------------------------------------------------
>
> Key: JENKINS-8214
> URL: https://issues.jenkins-ci.org/browse/JENKINS-8214
> Project: Jenkins
> Issue Type: Bug
> Components: core
> Environment: hudson 1.387 + Apache/modjk
> Reporter: Arnaud Héritier
>
> 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
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
