|
||||||||
|
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 |
||||||||
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
Parameters
In order to make sure for me (and prove for you and others) that I am getting everything right, let me describe my explanation of the issue you have.
So, we have 3 completely independent parameters that influence the issue:
Prediction
So here is the table of results you are getting together with my prediction based on my understanding of the issue:
Please make sure that everything is as described in the table.
Reasons
Why it fails for Version>1.530 for both OSes
According to https://wiki.jenkins-ci.org/display/JENKINS/Quick+and+Simple+Security , you should either grant additional permission for anonymous users or use a suggested plugin:
Why it works for Version<=1.530 for both OSes
Among the changes done after 1.530 release (see http://jenkins-ci.org/changelog for reference) there was one called "Use fine-grained permissions for node manipulation via REST API & CLI (issue 18485)". It changed the way how permission check works - so you need additional effort.
Why for Version>1.530 for both OSes it fails with 400 Error and not 403 or 404, which looks more appropriate in case if it is permission issue?
I guess it is due to multipart submission. I believe that in case if you use regular call it will return either 403 or 404 Error.
Hope it helps.
Feel free to post additional info in case if suggested recipe doesn't solve your issue.
Until that, I am going to consider it as solved.