Amazon S3 中的 Etag 定义已更改 [英] Etag definition changed in Amazon S3

查看:39
本文介绍了Amazon S3 中的 Etag 定义已更改的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我使用 Amazon S3 进行备份已有一段时间了.通常,在我上传文件后,我会检查 MD5 总和匹配,以确保我已做好备份.S3 有用于给出这个总和的etag"标头.

I've used Amazon S3 a little bit for backups for some time. Usually, after I upload a file I check the MD5 sum matches to ensure I've made a good backup. S3 has the "etag" header which used to give this sum.

但是,当我最近上传一个大文件时,Etag 似乎不再是 md5 总和.它有额外的数字和一个连字符 "696df35ad1161afbeb6ea667e5dd5dab-2861" .我找不到有关此更改的任何文档.我已经使用 S3 管理控制台和 Cyber​​duck 进行过检查.

However, when I uploaded a large file recently the Etag no longer seems to be a md5 sum. It has extra digits and a hyphen "696df35ad1161afbeb6ea667e5dd5dab-2861" . I can't find any documentation about this changing. I've checked using the S3 management console and with Cyberduck.

我找不到有关此更改的任何文档.有什么指点吗?

I can't find any documentation about this change. Any pointers?

推荐答案

如果任何文件使用 multipart 上传,那么您将始终获得这种类型的 ETag.但是,如果您将整个文件作为单个文件上传,那么您将像以前一样获得 ETag.

If any file is being uploaded with multipart then you will always get such type of ETag. But if you upload whole file as single file then you will get ETag as before.

Bucket Explorer 为您提供正常的 ETag,直到在分段操作中上传 5Gb.但更多的是它没有提供.

Bucket Explorer providing you normal ETag till 5Gb upload in multipart operation. But more then it is not providing.

AWS:

使用分段上传 api 创建的对象的 ETag 将包含一个或多个非十六进制字符和/或将由少于 16 个或多于 16 个十六进制数字组成.

The ETag for an object created using the multipart upload api will contain one or more non-hexadecimal characters and/or will consist of less than 16 or more than 16 hexadecimal digits.

参考:https://forums.aws.amazon.com/thread.jspa?messageID=203510#203510

这篇关于Amazon S3 中的 Etag 定义已更改的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆