[
https://issues.apache.org/jira/browse/LIBCLOUD-396?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13765448#comment-13765448
]
Tomaz Muraus commented on LIBCLOUD-396:
---------------------------------------
[~sfriesel] I gave it some thought and I'm not really a big fan of empty string
and None having a different meaning in this case. Imo, both should indicate "no
data".
In general I'm a big fan and proponent of "explicit is better than implicit",
but in this case I think it would be very easy to make a mistake.
> 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
