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

Andrew Gaul updated JCLOUDS-598:
--------------------------------

    Description: ParseSystemMetadataFromHeaders incorrectly looks for 
Content-MD5 instead of x-emc-wschecksum.  Note that the value has several 
formats and we should only parse those which have a MD5/0/ prefix.  Fixing this 
will allow removal of the overridden and disabled checkMD5 methods in 
AtmosContainerIntegrationLiveTest, AtmosIntegrationLiveTest, and AtmosLiveTest. 
 See b2016703adbc254347f0093171238b5f36e3fce4 for more context.  (was: 
ParseSystemMetadataFromHeaders incorrectly looks for Content-MD5 instead of 
x-emc-wschecksum.  Note that the value has has several formats and we should 
only parse those which have a MD5/0/ prefix.  Fixing this will allow removal of 
the overridden and disabled checkMD5 methods in 
AtmosContainerIntegrationLiveTest, AtmosIntegrationLiveTest, and AtmosLiveTest. 
 See b2016703adbc254347f0093171238b5f36e3fce4 for more context.)

> Atmos ParseSystemMetadataFromHeaders parses blob hash incorrectly
> -----------------------------------------------------------------
>
>                 Key: JCLOUDS-598
>                 URL: https://issues.apache.org/jira/browse/JCLOUDS-598
>             Project: jclouds
>          Issue Type: New Feature
>          Components: jclouds-blobstore
>    Affects Versions: 1.7.3
>            Reporter: Andrew Gaul
>            Assignee: Shri Javadekar
>            Priority: Minor
>
> ParseSystemMetadataFromHeaders incorrectly looks for Content-MD5 instead of 
> x-emc-wschecksum.  Note that the value has several formats and we should only 
> parse those which have a MD5/0/ prefix.  Fixing this will allow removal of 
> the overridden and disabled checkMD5 methods in 
> AtmosContainerIntegrationLiveTest, AtmosIntegrationLiveTest, and 
> AtmosLiveTest.  See b2016703adbc254347f0093171238b5f36e3fce4 for more context.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Reply via email to