Return valid md5 checksum in the header #205

New issue

Closed

opened 2023-09-07 14:38:10 +00:00 by alexvanin · 0 comments

alexvanin commented

2023-09-07 14:38:10 +00:00

Owner

Some libraries like jcloud, require md5 checksum in the e-tag or in the separate header. FrostFS S3 Gateway uses SHA-256 as e-tag and doesn't set md5 header, which leads to errors while using jcloud.

Describe the solution you'd like

Add a configuration flag to calculate valid md5 and store it in the tree service in S3 gateway runtime. Disable this behaviour by default.

!NB check if it is going to work with multipart upload objects

Describe alternatives you've considered

Replace e-tag encoding from SHA-256 to md5.

Additional context

Apps actually may not check md5 value at all. They might check only md5 format, nothing more.

## Is your feature request related to a problem? Please describe. Some libraries like [jcloud](https://github.com/apache/jclouds/blob/1252f1951f10c3bc47923184bbbb9d4aadc1b3fc/apis/s3/src/main/java/org/jclouds/s3/functions/ParseObjectMetadataFromHeaders.java#L66), require md5 checksum in the e-tag or in the separate header. FrostFS S3 Gateway uses SHA-256 as e-tag and doesn't set md5 header, which leads to errors while using jcloud. ## Describe the solution you'd like Add a configuration flag to calculate valid md5 and store it in the tree service in S3 gateway runtime. Disable this behaviour by default. > !NB check if it is going to work with multipart upload objects ## Describe alternatives you've considered Replace e-tag encoding from SHA-256 to md5. ## Additional context Apps actually may not check md5 value at all. They might check only md5 format, nothing more.