swift/hubic: document segmented object MD5SUM limitations - fixes #392

This commit is contained in:
Nick Craig-Wood 2016-03-16 17:39:44 +00:00
parent a1323eb204
commit 9dccf91da7
2 changed files with 14 additions and 3 deletions

View file

@ -1,7 +1,7 @@
---
title: "Hubic"
description: "Rclone docs for Hubic"
date: "2015-11-08"
date: "2016-03-16"
---
<i class="fa fa-space-shuttle"></i> Hubic
@ -115,5 +115,10 @@ are the same.
### Limitations ###
Code to refresh the OpenStack token isn't done yet which may cause
problems with very long transfers.
This uses the normal OpenStack Swift mechanism to refresh the Swift
API credentials and ignores the expires field returned by the Hubic
API.
The Swift API doesn't return a correct MD5SUM for segmented files
(Dynamic or Static Large Objects) so rclone won't check or use the
MD5SUM for these.

View file

@ -131,3 +131,9 @@ ns.
This is a defacto standard (used in the official python-swiftclient
amongst others) for storing the modification time for an object.
### Limitations ###
The Swift API doesn't return a correct MD5SUM for segmented files
(Dynamic or Static Large Objects) so rclone won't check or use the
MD5SUM for these.