From 0487e465ee4a65214d822162643ac64828960f8b Mon Sep 17 00:00:00 2001 From: dlitster Date: Tue, 25 Apr 2023 05:39:36 -0500 Subject: [PATCH] docs: s3: clarify that X-Amz-Meta-Md5chksum is really a base64-encoded hex --- docs/content/s3.md | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/docs/content/s3.md b/docs/content/s3.md index 2cd0adc93..0452bfa88 100644 --- a/docs/content/s3.md +++ b/docs/content/s3.md @@ -380,7 +380,11 @@ However for objects which were uploaded as multipart uploads or with server side encryption (SSE-AWS or SSE-C) the `ETag` header is no longer the MD5 sum of the data, so rclone adds an additional piece of metadata `X-Amz-Meta-Md5chksum` which is a base64 encoded MD5 hash (in -the same format as is required for `Content-MD5`). +the same format as is required for `Content-MD5`). You can use base64 -d and hexdump to check this value manually: + + echo 'VWTGdNx3LyXQDfA0e2Edxw==' | base64 -d | hexdump + +or you can use `rclone check` to verify the hashes are OK. For large objects, calculating this hash can take some time so the addition of this hash can be disabled with `--s3-disable-checksum`.