forked from docs/doc-exports
zhangyue
894279c39a
Reviewed-by: Hasko, Vladimir <vladimir.hasko@t-systems.com> Co-authored-by: zhangyue <zhangyue164@huawei.com> Co-committed-by: zhangyue <zhangyue164@huawei.com>
23 lines
1.5 KiB
HTML
23 lines
1.5 KiB
HTML
<a name="obs_03_0066"></a><a name="obs_03_0066"></a>
|
|
|
|
<h1 class="topictitle1">Delete Object</h1>
|
|
<div id="body1442650115392"><p id="obs_03_0066__p6499118610142">The <strong id="obs_03_0066__b18784032">DELETE</strong> command is used to delete a specified object. After an object is deleted, any subsequent GET, HEAD, POST, or DELETE operations return a <strong id="obs_03_0066__b842352706102656">404 Not Found</strong> error code.</p>
|
|
<p id="obs_03_0066__p66512805171514">For static large objects, you can add the <strong id="obs_03_0066__b34838562">multipart-manifest=delete</strong> query parameter. This operation deletes the segment objects and if all deletions succeed, this operation deletes the manifest object.</p>
|
|
<p id="obs_03_0066__p56332401171649">Normally the DELETE operation does not return a response body. However, with the <strong id="obs_03_0066__b1332161505151532">multipart-manifest=delete</strong> query parameter, the response body contains a list of manifest and segment objects and the status of their delete operations.</p>
|
|
</div>
|
|
<div>
|
|
<ul class="ullinks">
|
|
<li class="ulchildlink"><strong><a href="obs_03_0067.html">Request</a></strong><br>
|
|
</li>
|
|
<li class="ulchildlink"><strong><a href="obs_03_0068.html">Response</a></strong><br>
|
|
</li>
|
|
<li class="ulchildlink"><strong><a href="obs_03_0069.html">Examples</a></strong><br>
|
|
</li>
|
|
</ul>
|
|
|
|
<div class="familylinks">
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="obs_03_0053.html">Operations on Objects</a></div>
|
|
</div>
|
|
</div>
|
|
|