You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@libcloud.apache.org by "Tomaz Muraus (JIRA)" <ji...@apache.org> on 2012/10/14 02:02:05 UTC
[dev] [jira] [Closed] (LIBCLOUD-232) Atmos storage driver loses content
type during streaming upload
[ https://issues.apache.org/jira/browse/LIBCLOUD-232?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Tomaz Muraus closed LIBCLOUD-232.
---------------------------------
> Atmos storage driver loses content type during streaming upload
> ---------------------------------------------------------------
>
> Key: LIBCLOUD-232
> URL: https://issues.apache.org/jira/browse/LIBCLOUD-232
> Project: Libcloud
> Issue Type: Bug
> Components: Storage
> Affects Versions: 0.10.1
> Environment: All
> Reporter: Russell Keith-Magee
> Assignee: Tomaz Muraus
> Fix For: 0.11.0
>
>
> When you upload a file using upload_object(), the file/object name is interrogated to determine the mime type, and that mime type is then used when transferring the file.
> Following git commit 44dabc6404d38d77939aa446a331d0fa2d090a26, streaming uploads now work on the Atmos driver for new files. However, if you upload using streaming upload, the mime type isn't set on the uploaded object.
> This is important because if the mime type isn't provided, later downloads are all encoded application/octet-stream, which means the browser can only respond by downloading the object.
--
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