[
https://issues.apache.org/jira/browse/LIBCLOUD-396?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13765513#comment-13765513
]
Ivan edited comment on LIBCLOUD-396 at 9/12/13 3:19 PM:
--------------------------------------------------------
(Added new patch.) I think this is the best set of conditions, as it explicitly
references the raw argument. And raw argument has the description that should
explain what's happening. Aside from that, '' and None (for data) are treated
the same way.
was (Author: ikusalic):
I think this is the best set of conditions, as it explicitly references raw
argument. And raw argument has a the description that should explain what's
happening. Aside from that, '' and None (for data) are treated the same way.
(Added new patch.)
> 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-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
