You are viewing a plain text version of this content. The canonical link for it is here.

Posted to notifications@jclouds.apache.org by "Andrew Gaul (JIRA)" <ji...@apache.org> on 2015/02/25 05:05:04 UTC

[jira] [Closed] (JCLOUDS-180) Audit MD5 enforcement via new live tests

     [ https://issues.apache.org/jira/browse/JCLOUDS-180?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Andrew Gaul closed JCLOUDS-180.
-------------------------------
    Resolution: Duplicate

All BlobStores exercise this via {{BaseBlobIntegrationTest.testPutIncorrectContentMD5}} except for Atmos which we track in JCLOUDS-598.  See {{AtmosIntegrationLiveTest.checkMD5}} where we stub this out.

> Audit MD5 enforcement via new live tests
> ----------------------------------------
>
>                 Key: JCLOUDS-180
>                 URL: https://issues.apache.org/jira/browse/JCLOUDS-180
>             Project: jclouds
>          Issue Type: Improvement
>          Components: jclouds-blobstore
>            Reporter: Andrew Gaul
>            Assignee: Andrew Gaul
>
> We should audit MD5 enforcement via new live tests.  These tests should upload a blob with missing MD5, an incorrect MD5, and a correct MD5, for both authenticated putBlob and signed URL PUT.  Previously we encountered situations where providers like Atmos and Swift used different headers than Content-MD5 and did not benefit from this data integrity check.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)