Andrej Shadura 2422d3ab40 When ETag doesn’t look like MD5, use the value from metadata instead ...

The S3 backend relies on ETag S3 returns being equal to the MD5 of the
object, but it’s not necessarily true. When the value returned clearly
doesn’t look like a valid MD5 hash (length isn’t exactly 32 characters),
attempt to retrieve the MD5 hash possibly stored in the metadata.

We cannot always do this since user-defined metadata isn’t returned by
the ListObjects call, so verifying it for each object is expensive as it
requires one HEAD request per each object.

This commit fixes #923.

Signed-off-by: Andrej Shadura <andrew.shadura@collabora.co.uk>

2021-03-02 13:37:17 +00:00

..

public_test.go

Ignore 'NoSuchBucket' error when deleting S3 objects

2019-01-23 18:17:08 +03:00

public.go

When ETag doesn’t look like MD5, use the value from metadata instead

2021-03-02 13:37:17 +00:00

s3_test.go

gofmt -s

2015-02-22 14:29:09 +03:00

s3.go

Fix style issues. #15

2014-07-17 18:09:13 +04:00

server_test.go

Fix linter list and fix errors discovered by new staticcheck

2019-01-20 00:01:17 +03:00