Merge "Allow DLO manifest to be updated when using post-as-copy"
This commit is contained in:
doc/source
swift/common/middleware
test
@ -168,6 +168,12 @@ of segments to a second location and update the manifest to point to
|
||||
this new location. During the upload of the new segments, the original
|
||||
manifest is still available to download the first set of segments.
|
||||
|
||||
.. note::
|
||||
|
||||
When updating a manifest object using a POST request, a
|
||||
``X-Object-Manifest`` header must be included for the
|
||||
object to continue to behave as a manifest object.
|
||||
|
||||
**Example Upload segment of large object request: HTTP**
|
||||
|
||||
.. code::
|
||||
|
@ -57,6 +57,10 @@ Additional Notes
|
||||
<container>/<prefix>`` header will be returned with the concatenated object
|
||||
so you can tell where it's getting its segments from.
|
||||
|
||||
* When updating a manifest object using a POST request, a
|
||||
``X-Object-Manifest`` header must be included for the object to
|
||||
continue to behave as a manifest object.
|
||||
|
||||
* The response's ``Content-Length`` for a ``GET`` or ``HEAD`` on the manifest
|
||||
file will be the sum of all the segments in the ``<container>/<prefix>``
|
||||
listing, dynamically. So, uploading additional segments after the manifest is
|
||||
|
Reference in New Issue
Block a user