From a2f557e92103eb1b105db1099e10f38034a0609f Mon Sep 17 00:00:00 2001 From: Kazuhiro MIYAHARA Date: Wed, 6 Sep 2017 04:03:10 +0000 Subject: [PATCH] Add explanation about Content-Length header limit with DLO to docs If a number of DLO segments is larger than container listing limit, Content-Length header will not be included in GET or HEAD response. However, this fact is not explained in document of large objects. This patch add explanation about this fact to the document. Change-Id: Ia45fad05797f38fa8b6b0ed917b4f9d7fb337149 Closes-Bug: 1680219 --- doc/source/api/large_objects.rst | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/doc/source/api/large_objects.rst b/doc/source/api/large_objects.rst index 799e78848e..27f935c02a 100644 --- a/doc/source/api/large_objects.rst +++ b/doc/source/api/large_objects.rst @@ -149,7 +149,10 @@ tells Object Storage how to find the segment objects that comprise the large object. The segments remain individually addressable, but retrieving the manifest object streams all the segments concatenated. There is no limit to the number of segments that can be a part of a -single large object. +single large object, but ``Content-Length`` is included in **GET** or **HEAD** +response only if the number of segments is smaller than container listing +limit. In other words, the number of segments that fit within a single +container listing page. To ensure the download works correctly, you must upload all the object segments to the same container and ensure that each object name is