From 9dccf91da704cdc46e4f7223d3c3e5d28065a913 Mon Sep 17 00:00:00 2001
From: Nick Craig-Wood <nick@craig-wood.com>
Date: Wed, 16 Mar 2016 17:39:44 +0000
Subject: [PATCH] swift/hubic: document segmented object MD5SUM limitations -
 fixes #392

---
 docs/content/hubic.md | 11 ++++++++---
 docs/content/swift.md |  6 ++++++
 2 files changed, 14 insertions(+), 3 deletions(-)

diff --git a/docs/content/hubic.md b/docs/content/hubic.md
index a1c304853..d2e75dd47 100644
--- a/docs/content/hubic.md
+++ b/docs/content/hubic.md
@@ -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.
diff --git a/docs/content/swift.md b/docs/content/swift.md
index d14aa4f5f..e3b12090b 100644
--- a/docs/content/swift.md
+++ b/docs/content/swift.md
@@ -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.