> though I don't see why you won't consider this as part of the "S3 > specification"
That was indeed also part of the discussion ;-) I guess the key question to answer would be how many other "S3-compliant" providers also support it. I'd also be happy with having it in S3 (where it will hopefully end up), in which case I guess the signing code should be in [S3BlobRequestSigner](https://github.com/jclouds/jclouds/blob/master/apis/s3/src/main/java/org/jclouds/s3/blobstore/S3BlobRequestSigner.java) rather than a provider-specific AWSS3BlobRequestSigner class. I was moving this "down" (into AWS) rather than "up" (into S3) because the first commit had this logic at the provider level. --- Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds/pull/74#issuecomment-21581067
