[
https://issues.apache.org/jira/browse/JCLOUDS-254?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13756438#comment-13756438
]
ASF subversion and git services commented on JCLOUDS-254:
---------------------------------------------------------
Commit 3f2a196f269727faea732806807ea04043ca9126 in branch refs/heads/master
from [~nacx]
[
https://git-wip-us.apache.org/repos/asf?p=incubator-jclouds-chef.git;h=3f2a196 ]
JCLOUDS-245/JCLOUDS-254: Fix live tests
Refactored the domain model to be immutable and addressed some
inconsistences with the Chef Server API model.
Removed all HEAD methods, as they have been removed from newer versions
of Chef. They were used to test the existance of a given resource, and
with newer versions the only way to do that is via a GET operation.
Now all live tests are passing for Community Chef 0.10.8, 11.0.6 and
Enterprise Chef.
> Cookbook download fails if URLs have encoded characters in the signature
> ------------------------------------------------------------------------
>
> Key: JCLOUDS-254
> URL: https://issues.apache.org/jira/browse/JCLOUDS-254
> Project: jclouds
> Issue Type: Bug
> Components: jclouds-chef
> Affects Versions: 1.7.0, 1.6.1
> Reporter: Ignasi Barrera
> Assignee: Ignasi Barrera
> Labels: enterprisechef
>
> In Enterprise Chef and Chef 11, the storage for the cookbook files has
> changed. Now the URLs to download the file are signed URLs that are outside
> the Chef Server (in S3, for example).
> If those URLs contain URL encoded characters in the 'Signature' query
> parameter, the request is generated with an invalid signature. There is a
> discussion [1] in the chef-dev mailing list to understand the details of how
> those characters should be treated when signing the requests, so we can
> properly add the appropriate changes.
> [1] http://lists.opscode.com/sympa/arc/chef-dev/2013-08/msg00028.html
--
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
