From cad436fb951dcb5d1c943e2ae6f336ded36fa4a4 Mon Sep 17 00:00:00 2001 From: Andrew Gaul Date: Wed, 2 Sep 2015 11:26:39 -0700 Subject: [PATCH] Do not set Content-MD5 during copy part The previously used MD5 covered the entire object, not just the range request. Uncovered by ceph/s3-tests#75. --- src/main/java/org/gaul/s3proxy/S3ProxyHandler.java | 3 --- 1 file changed, 3 deletions(-) diff --git a/src/main/java/org/gaul/s3proxy/S3ProxyHandler.java b/src/main/java/org/gaul/s3proxy/S3ProxyHandler.java index d9d06af..45d4997 100644 --- a/src/main/java/org/gaul/s3proxy/S3ProxyHandler.java +++ b/src/main/java/org/gaul/s3proxy/S3ProxyHandler.java @@ -1597,8 +1597,6 @@ final class S3ProxyHandler extends AbstractHandler { BlobMetadata blobMetadata = blob.getMetadata(); long contentLength = blobMetadata.getContentMetadata().getContentLength(); - HashCode contentMD5 = - blobMetadata.getContentMetadata().getContentMD5AsHashCode(); String eTag; try (InputStream is = blob.getPayload().openStream()) { @@ -1626,7 +1624,6 @@ final class S3ProxyHandler extends AbstractHandler { } else { Payload payload = Payloads.newInputStreamPayload(is); payload.getContentMetadata().setContentLength(contentLength); - payload.getContentMetadata().setContentMD5(contentMD5); MultipartPart part = blobStore.uploadMultipartPart(mpu, partNumber, payload);