openstack/swift
Code Issues Proposed changes

Add explanation about Content-Length header limit with DLO to docs

Browse Source 
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
This commit is contained in:
Kazuhiro MIYAHARA 2017-09-06 04:03:10 +00:00
parent 6da17e9923
commit a2f557e921
1 changed files with 4 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
doc/source/api/large_objects.rst
View File

@ -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