|
||||||||||||||||
|
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.
This issue is caused by the fix to a security issue, see the advisory. It also explains how to work around that problem. However, a better solution exists since 1.537 in Plugins providing an implementation of the SecureRequester interface, e.g.:
https://wiki.jenkins-ci.org/display/JENKINS/Secure+Requester+Whitelist+Plugin
I'm resolving this as not a defect, because it's a deliberate change because of security concerns. That it shows a content decoding error instead of "Access Denied" is a different, less important issue.