[
https://issues.apache.org/jira/browse/LIBCLOUD-396?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13765640#comment-13765640
]
ASF subversion and git services commented on LIBCLOUD-396:
----------------------------------------------------------
Commit 7179aacecebd3a0be303e59b49c5fc946200bb88 in branch refs/heads/trunk from
[~ikusalic]
[ https://git-wip-us.apache.org/repos/asf?p=libcloud.git;h=7179aac ]
LIBCLOUD-396: Do not set Content-Length if present in raw requests
Signed-off-by: Tomaz Muraus <[email protected]>
> 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
