|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
- [JIRA] (JENKINS-16099) Not able to enter correct S... [email protected] (JIRA)
- [JIRA] (JENKINS-16099) Not able to enter corr... [email protected] (JIRA)
- [JIRA] (JENKINS-16099) Not able to enter corr... [email protected] (JIRA)
- [JIRA] (JENKINS-16099) Not able to enter corr... [email protected] (JIRA)
- [JIRA] (JENKINS-16099) Not able to enter corr... [email protected] (JIRA)
- [JIRA] (JENKINS-16099) Not able to enter corr... [email protected] (JIRA)
- [JIRA] (JENKINS-16099) Not able to enter corr... [email protected] (JIRA)
- [JIRA] (JENKINS-16099) Not able to enter corr... [email protected] (JIRA)
- [JIRA] (JENKINS-16099) Not able to enter corr... [email protected] (JIRA)
- [JIRA] (JENKINS-16099) Not able to enter corr... [email protected] (JIRA)
- [JIRA] (JENKINS-16099) Not able to enter corr... [email protected] (JIRA)

OK, I think the issue is at step 4 -the code returned by our SVN repo is not a 401, but a 403 (FORBIDDEN)
I know the HTTP spec tells to return a 401 if the request contains the credentials, but what stops us from doing same thing for a 403 as we do in case of a 401?