[
https://issues.apache.org/jira/browse/JCLOUDS-1501?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Blagoi Anastasov updated JCLOUDS-1501:
--------------------------------------
Description:
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.
was:
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 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.
> 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
> Affects Versions: 2.1.2
> Reporter: Blagoi Anastasov
> Priority: Major
> Fix For: 2.1.3
>
>
> 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.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
