[
https://issues.apache.org/jira/browse/JCLOUDS-1213?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15819508#comment-15819508
]
Andrew Gaul commented on JCLOUDS-1213:
--------------------------------------
This same code works for me using 2.1.0-SNAPSHOT. Abbreviated wire logs:
{code}
>> GET https://gaultest-eu2.s3.amazonaws.com/?location HTTP/1.1
>> Authorization: AWS4-HMAC-SHA256
>> Credential=AKIAITMZ4YFWHBLA4KMA/20170111/us-east-1/s3/aws4_request,
>> SignedHeaders=host;x-amz-content-sha256;x-amz-date,
>> Signature=1a5d2a283b463caa68eb10960f012583a7564eb5d34bb0c5237a3fe532c15314
<< HTTP/1.1 200 OK
>> GET https://gaultest-eu2.s3-eu-west-1.amazonaws.com/?delimiter=/ HTTP/1.1
>> Authorization: AWS4-HMAC-SHA256
>> Credential=AKIAITMZ4YFWHBLA4KMA/20170111/eu-west-1/s3/aws4_request,
>> SignedHeaders=host;x-amz-content-sha256;x-amz-date,
>> Signature=8b9a629cb5fb973bec6b625bf5ad9a0d24dda45716ede3116be4d3318558760f
<< HTTP/1.1 200 OK
<< x-amz-bucket-region: eu-west-1
{code}
> S3: Region is not respected
> ---------------------------
>
> Key: JCLOUDS-1213
> URL: https://issues.apache.org/jira/browse/JCLOUDS-1213
> Project: jclouds
> Issue Type: Bug
> Components: jclouds-blobstore
> Affects Versions: 2.0.0
> Reporter: Halvdan Hoem Grelland
> Labels: aws-s3
>
> When using a BlobStore configured for the 'aws-s3' provider and with an
> explicit region ('eu-west-1' in this case),
> _BlobStore.createContainerInLocation(Location location, String container)_
> fails with a 400 when attempting to create an already existing bucket on that
> location.
> The error message from AWS claims the cause to be
> _AuthorizationHeaderMalformed_, and says that 'eu-west-1' was expected, but
> that 'us-east-1' was supplied in the PUT request.
> I have confirmed that 'eu-west-1' is, in fact, given to the method call, but
> it does not seem to be respected when forming and signing the request.
> This does not happen on 1.9.x.
> From the debugging i have done a likely culprit seems to be
> _Aws4SignerForAuthorizationHeader_ which resolves a _ServiceAndRegion_
> instance, which in turn seem to attempt parsing the region from the hostname
> URL (_AWSHostNameUtils.parseRegionName(..)_). I cannot see the region set for
> the provider being respected in this case.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
