(my search in the console had garbage I didn't notice)

makes me wonder why every other S3 provider accepts that fine

> The x-amz-content-sha256 header is required for all AWS Signature Version 4 requests. It provides a hash of the request payload. If there is no payload, you must provide the hash of an empty string.

Even in streaming chunked mode it's required (

STREAMING-AWS4-HMAC-SHA256-PAYLOAD

)

Yeah it's strange it doesn't send it

managed to find https://github.com/rclone/rclone/issues/5422

they note that it sends

content-md5

instead, among other things

That's not sufficient though. They should be sending

x-amz-content-sha256: UNSIGNED-PAYLOAD

instead

I see, thanks for the assistance

np

Footnote 1 is correct. The object size limit is

5TB - around 5GB

. The max upload size if

5GB - around 5 MB

Out of curiosity, why is that?

(Just wondering)

Encryption overhead

Our storage nodes have a 5TB and 5GB limit and we have encryption overhead that steals a little bit away from that.

Cool.

ah that's true - good point

I decided to clone the rclone source and add that header to see what happens, now its getting

xml
<Error>
  <Code>InvalidArgument</Code>
  <Message>Invalid Argument: Date</Message>
</Error>

With

Headers:
x-amz-acl:             private
x-amz-content-sha256:  UNSIGNED-PAYLOAD
user-agent:            rclone/v1.59.0-DEV
content-md5:           sFQDISxmvcjMxZf+32zV/g==
content-type:          text/plain; charset=utf-8
x-amz-meta-mtime:      1651242675.438993951
content-length:        10
accept-encoding:       gzip

Query:
X-Amz-Algorithm:     AWS4-HMAC-SHA256
X-Amz-Credential:    credentialhere/20220429/us-east-1/s3/aws4_request
X-Amz-Date:          20220429T150928Z
X-Amz-Expires:       900
X-Amz-SignedHeaders: content-md5;content-type;host;x-amz-acl;x-amz-meta-mtime
X-Amz-Signature:     signaturehere

I'm not overly familiar with S3 API but I'm not 100% sure what it wants because

X-Amz-Date

and the date in the credential seem to follow whats here

Uggh. I have a fix up that'll help clarify those kinds of errors

I think it means the signed date in the credential isn't matching... which it clearly is

wtf

I'll make sure the next release has more helpful info

I guess a 0-length list query could be used to check if there's any objects in the bucket without actually retrieving it? It really is a weird edge case.

Dropshare still isn’t happy… 😦

DM me the account tag

not to be pushy or impatient but is there an estimated ETA/completion percentage (Q3/Q4 2022, 85% done, etc?) for the open beta? (or whatever its gonna be called)

Ok i'm playing with the s3 api

and....