[ 
https://issues.apache.org/jira/browse/JCLOUDS-250?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13749664#comment-13749664
 ] 

ASF subversion and git services commented on JCLOUDS-250:
---------------------------------------------------------

Commit d05e77b8b6bfb8f5f56d3f4b38fd7344360a2832 in branch refs/heads/master 
from [~francis]
[ https://git-wip-us.apache.org/repos/asf?p=incubator-jclouds.git;h=d05e77b ]

Fix JCLOUDS-250 for the common case where blob names do not contain /

                
> Swift: Uploading a blob whose name starts with the name of a multipart blob 
> changes the multipart blob's contents
> -----------------------------------------------------------------------------------------------------------------
>
>                 Key: JCLOUDS-250
>                 URL: https://issues.apache.org/jira/browse/JCLOUDS-250
>             Project: jclouds
>          Issue Type: Bug
>          Components: jclouds-blobstore
>            Reporter: Francis Devereux
>
> If you upload a multipart blob named "foo" and then upload a non-multipart 
> blob named "foo.bar" to the same container then when you get the contents of 
> "foo" they will include the contents of "foo.bar".
> This happens because CommonSwiftAsyncClient uses the blob's name as the value 
> for the X-Object-Manifest header, and swift includes all blobs whose names 
> start with this value when responding to a GET on the multipart blob.
> http://docs.openstack.org/trunk/openstack-object-storage/admin/content/direct-api-management-of-large-objects.html
>  and 
> http://www.rackspace.com/blog/rackspace-cloud-files-now-supporting-extremely-large-file-sizes/
>  append a / to the end of the X-Object-Manifest header which avoids this 
> issue in the common case (it can still happen if a blob with / in the name is 
> uploaded, but this is likely to be uncommon because / does not commonly 
> appear in filenames as it is the UNIX path separator character).

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Reply via email to