libcloud-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Stefan Friesel (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (LIBCLOUD-396) Commit c10249d1d733ba5215820c5d935265de5ae6bc84 break SWIFT storage
Date Thu, 12 Sep 2013 13:40:52 GMT

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

Stefan Friesel commented on LIBCLOUD-396:
-----------------------------------------

The function storage.common.base._upload_object is doing just that. It sets data=None and
Content-Length to a non-zero value when calling request(). The data itself is then sent after
the call to request() by calling a upload_func callback. So other drivers using this base
function may be afected as well.
                
> Commit c10249d1d733ba5215820c5d935265de5ae6bc84 break SWIFT storage
> -------------------------------------------------------------------
>
>                 Key: LIBCLOUD-396
>                 URL: https://issues.apache.org/jira/browse/LIBCLOUD-396
>             Project: Libcloud
>          Issue Type: Bug
>          Components: Storage
>    Affects Versions: 0.13.1
>            Reporter: Ivan
>         Attachments: 0001-Set-Content-Length-to-0-only-if-it-is-not-set.patch
>
>
> Commit c10249d1d733ba5215820c5d935265de5ae6bc84 break SWIFT storage (Provider.CLOUDFILES_SWIFT).
> The commit sets the Content-Length to 0 which can overwrite the existing content length
(in libcloud/common/base.py).
> The proposed fix: set the length to 0 only if it is not already set.

--
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

Mime
View raw message