-
-
Notifications
You must be signed in to change notification settings - Fork 903
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Cloudflare R2: WARNING: MD5 Sums don't match! #1273
Comments
Sadly, there is not so much we can do at the moment if Cloudflare does not fix their api. I think that you can still use s3cmd with the following flag: "--no-check-md5". You will not have the md5 checked for "sync", but if you only use "put", that should not change too much. Also, if you are willing to give a try to a hack to the source code of s3cmd, you can try to do something: For example here: Line 1844 in b7520e5
Currently, in the code, we have some detection for ETAGs that are not "hash", and to overcome that we our own customer header. But we do that by detecting the character "-" inside the value. Because, on AWS, for multipart parts there will be a minus with the number of the part. If the modification works, you can give a try asking Cloudflare if, by chance, they would not want to change their "ETAG" to one with a syntax that match what is expected.
|
Is this about the ETag for UploadPart or for the completed download? For UploadPart we're not going to be returning the MD5 and that's an intentional deviation. If that's the case, so far I've only heard of s3cmd having an issue. For completed multipart we return |
@vlovich Yes, here we are speaking about the ETag of the UploadPart. But, for a single part upload, there is no reason that the ETag behavior would not be the same as for a simple non-multipart file. We might try to detect that it is not a md5 based on the size, but it is a little bit sad to have to do a hack just because of Cloudflare implementation... |
anyone know if this issue has been fixed. I'm looking to upload large files to R2 |
Happens when upload large (>5G) files that require multi part upload to Cloudflare R2.
Maybe Cloudflare is missing API compatability? Docs looks ok to me
https://developers.cloudflare.com/r2/platform/s3-compatibility/api/#object-level-operations
Issue in Cloudflare Community forums: https://community.cloudflare.com/t/multi-part-uploads-from-s3cmd-broken/412143
The text was updated successfully, but these errors were encountered: