@john.spurlock I assume S3 just echoes back your

ContinuationToken

in

NextContinuationToken

right? Or does it never echo back a

NextContinuationToken

?

What info would be required to work out why rclone isn't working btw? It works fine with every other S3 provider so I doubt they're doing anything too badly wrong and I'd love to get it working

I'm assuming you're asking about sigv4?

I'm not 100% sure, It can list and get files but upload throws 401

That's very surprising

albert showed some request data earlier, i can grab more if needed

gonna run mitmproxy myself now and dump the full thing

Is rclone uploading in streaming sigv4 mode?

don't you mean TB and GB in footnote 1? Also "its" not "it's" in footnote 2 : )

I've never used this excuse in my life before since I grew up in Canada since the age of 5, but I think I'm at the point in my life where I'll just start saying "English isn't my first language".

no when max-keys is 0, they don't return a NextContinuationToken at all

there's nothing really to continue : )

Hey, fellow Canadian! 👋 🇨🇦

2022-04-29 15:32:35 PUT https://ece1d09b06af2ced51407c97505ea0cc.r2.cloudflarestorage.com/erisa/file.txt?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=keygoeshere%2Fus-east-1%2Fs3%2Faws4_request&X-Amz-Date=20220429T143235Z&X-Amz-Expires=900&X-Amz-SignedHeaders=content-md5%3Bcontent-type%3Bhost%3Bx-amz-acl%3Bx-amz-meta-mtime&X-Amz-Signature=signaturehere HTTP/2.0

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

after formatting that i found a better way it shows the query params so the same query params are prettified as

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

response is 401

xml
<Error>
  <Code>Unauthorized</Code>
  <Message>Unauthorized</Message>
</Error>

I mean kind of there is - it's just a cursor in between keys

and when it lists files it succeeds doing

2022-04-29 15:37:56 GET https://ece1d09b06af2ced51407c97505ea0cc.r2.cloudflarestorage.com/erisa?delimiter=&max-keys=1

user-agent:            rclone/v1.53.3-DEV
x-amz-date:            20220429T143756Z
x-amz-content-sha256:  redacted_dontknowifitssensitive
authorization:         AWS4-HMAC-SHA256
                       Credential=credentialgoeshere/20220429/us-east-1/s3/aws4_request,
                       SignedHeaders=host;x-amz-content-sha256;x-amz-date,
                       Signature=signaturegoeshere
accept-encoding:       gzip

1 sec

or before the first key? sending max-keys = 0 is admittedly an edge case but it makes sense to me that there would be no subsequent "page"

Can you retry that PUT? I want to see what our logs say

There would be because your next request could send a different limit

retried, it tries 3 times so theres multiple sorry

Grrr... I'm not seeing it in the logs

Can you do it more?

done 3 more

There's a lot of traffic

you cant filter by my account ID?

i told rclone to retry 100 times and left it running, enjoy

100 requests done

missing x-amz-content-sha256