see if that is faster

Hello, I have a question about r2 object's checksums. When put or completing a multi-upload, if a checksum is supplied, does r2 verify the checksum (as oppose to simply record as a metadata)?

Genius UI design to maximise user retention

Hi, I need help getting access to the files stored on my R2. When accessing the bucket through the subdomain I get this:

And when accessing it through the URL given by R2 I get this:

I am developing in Unity (C#) and I need my files to be accessable through that

Can anyone help me?

Public URL Access: Allowed

You need to load a specific file, not just the subdomain itself. If you have a file called

myimage.png

in your bucket, you can access it at

https://[your r2 subdomain].r2.dev/myimage.png

.

What command are you running?

It's got nothing to do with retention, we have no incentive to keep people on the dashboard. If anything, people spending time on the UI is more frustrating for them. The reason you cannot "empty-and-delete" a bucket is because deleting (potentially) millions of objects cannot be made instantaneous. This creates a bunch of non-trivial technical/product/billing problems. Instead of releasing something janky and unpredictable, we decided to let users control their objects (for now). There's a reason why even S3 has this limitation.

You won't be able to validate the checksum of the entire multipart upload when completing, but you should be able to verify checksums of individual parts as you upload them. Would that work for you?

Looks like you might be using the S3 API's URL (.r2.cloudflarestorage.com) expecting it to behave like a public bucket's URL (.r2.dev or a custom domain)?

Thanks this worked haha

I get this when enabling IP filtering: 2023/04/03 18:48:06 Failed to ls: InternalError: We encountered an internal error. Please try again. status code: 500, request id: , host id:

Yes my IP is correct, both IPv4 and IPv6

You're the same guy as before. https://discord.com/channels/595317990191398933/940663374377783388/1088608444505923615 Did you ever get a chance to try --bind={your_ipv4} (or disabling IPv6 just to test)?

I’m still struggling with this issue: https://community.cloudflare.com/t/cannot-delete-r2-custom-domain/421058/3 Would anyone be able to help getting rid of this record?

Right yes, sorry I forgot to try your command as I was in bed when I read it.

No worries, just curious if my suspicious are correct and IP filtering only works over IPv4

Bind works!

Any way to make it default behaviour in the config file?

Not that I know of. If It truly does not support IPv6 IP Filtering over the S3 API, that's a bug that should be fixed imo. I haven't done enough testing to be 100% sure that it is though, could be something rclone specific or something weird like that.

In my case, the client includes the checksum for the entire content in its request to complete the upload. As such just verifying the parts won't work for me. Does it mean I have to conduct the verification myself? It's a bit more code, not a big deal. But then is there anyway to attach the checksum metadata? (I notice the s3 api supports a x-amz-checksum-algorithm query param, is this supported in r2?)

Anyone has an update on this? Not having any kind on integrity check is not good... https://community.cloudflare.com/t/does-r2-support-checksum-when-uploading-doesnt-seem-so/488674 I have a few big files (100MB+) that keep getting uploaded incorrectly...

I'm uploading the files like this:

csharp
                var fileTransferUtility = new TransferUtility(s3client);
            
                var uploadRequest = new TransferUtilityUploadRequest
                {
                    Key = fileKey,
                    FilePath = $"{filePath}",
                    BucketName = settings.CloudflareR2BucketName,
                    DisablePayloadSigning = true,
                    ContentType = "application/octet-stream",
                    DisableMD5Stream = true,
                    Headers =
                    {
                        ["if-none-match"] = $"\"{md5}\"",
                    }
                };

                Console.WriteLine("\nUploading file {0} ({1:N0} bytes)", file.FileName, new FileInfo($"{filePath}").Length);

                using var progress = new ProgressBar();
                
                uploadRequest.UploadProgressEvent += 
                    (_, e) => progress.Report(e.TransferredBytes / (double) e.TotalBytes); 

                await fileTransferUtility.UploadAsync(uploadRequest);

It's only happening with all files above 100MB, the MD5 uploaded doesn't match the local one...

Sounds like it's using multipart uploads above 100MB

and doesn't cloudflare support multipart uploads?

It does, but not clear how it handles checksum. I have a similar question above.