Daniel Beck resolved Bug JENKINS-20612 as Cannot Reproduce

Cannot reproduce the problem in 1.577. Is it that the error is not reported in JSON?

  • It sets HTTP 403 in the response, and adds headers explaining what permissions are missing, e.g. X-Required-Permission: hudson.model.Hudson.Read or X-You-Are-Authenticated-As: anonymous. So that alone can be used by clients to determine something went wrong and it's permissions related.
  • I doubt a completely unexpected JSON object explaining the permissions issue would be more helpful. Looking at the headers should be easy enough.

Or is it that it's too difficult to determine for human users what the issue is?

The complete output (sans headers) looks like the following:

<html><head><meta http-equiv='refresh' content='1;url="" style='background-color:white; color:white;'>


Authentication required
<!--
You are authenticated as: anonymous
Groups that you are in:
  
Permission you need to have (but didn't): hudson.model.Hudson.Read
 ... which is implied by: hudson.security.Permission.GenericRead
 ... which is implied by: hudson.model.Hudson.Administer
-->

* Closing connection 0
</body></html>

So it's quite obvious again, that it's permissions related.

Change By: Daniel Beck (01/Sep/14 10:02 PM)
Status: Open Resolved
Resolution: Cannot Reproduce
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 [email protected].
For more options, visit https://groups.google.com/d/optout.

Reply via email to