Timur Alperovich
Timur Alperovich
I know there is an issue if jclouds.endpoint is set to an empty string, but this configuration succeeds for me: ``` jclouds.provider=azureblob jclouds.azureblob_auth=azureKey jclouds.identity= jclouds.credential= s3proxy.authorization=aws-v4 s3proxy.identity=foo s3proxy.credential=bar s3proxy.endpoint=http://localhost:10080 ```...
AWS supports two signing methods for S3 requests: v2 (deprecated - https://docs.aws.amazon.com/general/latest/gr/signature-version-2.html) and v4 (https://docs.aws.amazon.com/general/latest/gr/signature-version-4.html). Setting the value to aws-v2-or-v4 instructs s3proxy to verify both kind of signatures for an...
Thanks for the report! This has come up a few times. To start, s3proxy shouldn't return a 500 error in this case. I _think_ Azure returns 400, but need to...
@gaul I'll need to reload this into my brain. Will try to check it out over the weekend.