[ https://issues.apache.org/jira/browse/JCLOUDS-1594?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17474519#comment-17474519 ]
ASF subversion and git services commented on JCLOUDS-1594: ---------------------------------------------------------- Commit 468b126dd856b48ff89f423b649ec4e3b19af012 in jclouds's branch refs/heads/master from Andrew Gaul [ https://gitbox.apache.org/repos/asf?p=jclouds.git;h=468b126 ] JCLOUDS-1594: Allow overriding S3 signer Previously s3 always used v2 and aws-s3 always used v4. Now s3 defaults to v2 and can override to v4. Note that this does not change BlobRequestSigner. > Allow overriding S3 with V4 signing > ----------------------------------- > > Key: JCLOUDS-1594 > URL: https://issues.apache.org/jira/browse/JCLOUDS-1594 > Project: jclouds > Issue Type: Improvement > Components: jclouds-blobstore > Affects Versions: 2.4.0 > Reporter: Andrew Gaul > Assignee: Andrew Gaul > Priority: Major > Labels: s3 > Time Spent: 20m > Remaining Estimate: 0h > > Currently the S3 provider can only use the V2 signer while AWS can only use > the V4 signer. Allowing configuration of the former will improve > compatibility with some non-AWS services that don't allow V2. -- This message was sent by Atlassian Jira (v8.20.1#820001)