jclouds-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andrew Gaul (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (JCLOUDS-378) compare Etag against MD5 after BlobStore.putBlob
Date Thu, 22 Jan 2015 18:41:35 GMT

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

Andrew Gaul updated JCLOUDS-378:
    Assignee:     (was: Andrew Gaul)

> compare Etag against MD5 after BlobStore.putBlob
> ------------------------------------------------
>                 Key: JCLOUDS-378
>                 URL: https://issues.apache.org/jira/browse/JCLOUDS-378
>             Project: jclouds
>          Issue Type: Improvement
>          Components: jclouds-blobstore
>    Affects Versions: 1.6.2
>            Reporter: Andrew Gaul
>            Priority: Minor
> Presently jclouds sends the Content-MD5 to the blobstore when provided by the caller.
 This allows the blobstore to reject corrupt or incomplete requests.  jclouds could do more
for streaming requests without Content-MD5 by calculating the MD5 as it sends it to the blobstore.
 When the blobstore returns the Etag, jclouds could compare this against the calculated MD5.
 Note that Amazon S3 supports this feature and the amazonaws bindings throw an exception to
the caller.

This message was sent by Atlassian JIRA

View raw message