Invalid S3 Checksum about activestorage HOT 6 CLOSED

On Jul 5, 2017, at 21:40, johnwilliams ***@***.***> wrote: Using the etag of an object is not a valid checksum of an S3 object if the object was multipart uploaded. If an object is created by either the Multipart Upload or Part Copy operation, the ETag is not an MD5 digest, regardless of the method of encryption. http://docs.aws.amazon.com/AmazonS3/latest/API/RESTCommonResponseHeaders.html This also raises another question in my mind. Should we be checking the checksum of a file before it gets uploaded to ensure that the file was not corrupted in transit? It is recommended and supported by S3 and GCS. — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub, or mute the thread.

On Jul 5, 2017, at 23:13, johnwilliams ***@***.***> wrote: @dhh They are triggered based on file size by the S3 lib. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or mute the thread.

On Thu, Jul 6, 2017 at 3:30 PM, johnwilliams ***@***.***> wrote: I pondered this overnight and I think the proper thing to do here (if we want to track checksums) is to compute the md5sum of the uploaded IO. Then upload with checksum included so GCS or S3. This will give verification that the file was uploaded and stored as we expected. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#2 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAAKtWctaFlqMXHx-H165aUrEy5GIItOks5sLOGMgaJpZM4OOx0l> .