You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@jclouds.apache.org by "Bhathiya Supun (JIRA)" <ji...@apache.org> on 2014/03/20 14:32:44 UTC
[jira] [Commented] (JCLOUDS-180) Audit MD5 enforcement via new live
tests
[ https://issues.apache.org/jira/browse/JCLOUDS-180?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13941719#comment-13941719 ]
Bhathiya Supun commented on JCLOUDS-180:
----------------------------------------
I like to work on this issue,Where it stands now?(I am asking because issue is created 8 months back and things may have change).
> 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 shoud 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.2#6252)