Re: AWS v4 Signature algorithm required for generic-S3

2020-12-10 Thread John Calcote
I see someone asked this very question a while back (2018): 
https://lists.apache.org/thread.html/3553946dcbe7c72fc8f82c6353c9a5c56d7b587da18a4ebe12df1e26%40%3Cuser.jclouds.apache.org%3E

Did anyone ever solve the double read issue regarding disabling data-hashing?

On 2020/12/10 18:03:13, John Calcote  wrote: 
> Hi all - 
> 
> We have a client who would like to use jclouds with ONTAP 9.8, which requires 
> V4 signatures AND path-based URL naming. I believe the true AWS S3 provider 
> requires virtual bucket URL naming. Anyone have any ideas on how to either:
> 
> 1) coerce jclouds into using the AWS S3 provider with path-based naming or
> 2) coerce jclouds into using the generic S3 provider with V4 signing
> 
> Thanks in advance.
> John
> 


AWS v4 Signature algorithm required for generic-S3

2020-12-10 Thread John Calcote
Hi all - 

We have a client who would like to use jclouds with ONTAP 9.8, which requires 
V4 signatures AND path-based URL naming. I believe the true AWS S3 provider 
requires virtual bucket URL naming. Anyone have any ideas on how to either:

1) coerce jclouds into using the AWS S3 provider with path-based naming or
2) coerce jclouds into using the generic S3 provider with V4 signing

Thanks in advance.
John