You are viewing a plain text version of this content. The canonical link for it is here.

Posted to notifications@libcloud.apache.org by "Tomaz Muraus (JIRA)" <ji...@apache.org> on 2013/09/18 21:45:52 UTC

[jira] [Resolved] (LIBCLOUD-396) Commit c10249d1d733ba5215820c5d935265de5ae6bc84 break SWIFT storage

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

Tomaz Muraus resolved LIBCLOUD-396.
-----------------------------------

       Resolution: Fixed
    Fix Version/s: 0.13.2
    
> 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
>             Fix For: 0.13.2
>
>         Attachments: 0001-Do-not-set-Content-Length-if-present-in-raw-requests.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