[jira] [Commented] (JCLOUDS-1501) S3 SignatureDoesNotMatch when trying to get the response from GET Request

["Andrew Gaul (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/JCLOUDS-1501?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16862408#comment-16862408 ] 

Andrew Gaul commented on JCLOUDS-1501:
--------------------------------------

Which S3 implementation do you test against?  Also I believe that the S3 provider defaults to V2 signing; do you override this?  Can you share some trace level logging?

> S3 SignatureDoesNotMatch when trying to get the response from GET Request
> -------------------------------------------------------------------------
>
>                 Key: JCLOUDS-1501
>                 URL: https://issues.apache.org/jira/browse/JCLOUDS-1501
>             Project: jclouds
>          Issue Type: Bug
>          Components: jclouds-blobstore
>    Affects Versions: 2.1.2
>            Reporter: Blagoi Anastasov
>            Priority: Major
>              Labels: s3
>
> HttpRequest request = {color:#660e7a}mBlobStoreContext{color}.getSigner()
>  .signGetBlob({color:#660e7a}mBeanConfigurations{color}.getS3Bucket(), targetObjectKey);
>  HttpResponse response = {color:#660e7a}mBlobStoreContext{color}.utils().http().invoke(request);
>  
> When pointing to s3 custom endpoint and trying to get the response from the GET Request it fails with SignatureDoesNotMatch message in the AWSResponseException. Strange behavior is that it has no issues while PUT requests so it has nothing wrong with the Access Key and the Secret Key. 
> V4 Signature is used for Authorization.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)