Bug #16830

[keep-web] S3 PutObject response should have content MD5

Added by Tom Clegg about 2 months ago.

Status:
New
Priority:
Normal
Assigned To:
-
Category:
-
Target version:
Start date:
Due date:
% Done:

0%

Estimated time:
Story points:
-

Description

Currently s3cmd can upload a file to keep-web successfully, but the response does not have an ETag header with the expected content MD5, so s3cmd counts it as a failure and retries.

Response header should look like

ETag: "1b2cf535f27731c974343645a3985328" 

https://docs.aws.amazon.com/AmazonS3/latest/API/API_PutObject.html


Related issues

Related to Arvados Epics - Story #16360: Keep-web supports S3 compatible interfaceIn Progress07/01/202011/18/2020

History

#1 Updated by Tom Clegg about 2 months ago

  • Related to Story #16360: Keep-web supports S3 compatible interface added

Also available in: Atom PDF