You can retrieve the manifest object itself (as opposed to the concatenated segments that it points to) by using a multipart-manifest=get query string with a GET or HEAD request. See [1].
Otherwise, RFC 7231 [2] disallows sending different response headers for a HEAD than a GET so if the GET for a DLO does not resolve the segments and returns 404, the HEAD must do the same.
There is a note here [3] that segments must be sync'd as well as manifests [3], but it could be clearer that the source and target container names must be the same.
You can retrieve the manifest object itself (as opposed to the concatenated segments that it points to) by using a multipart- manifest= get query string with a GET or HEAD request. See [1].
Otherwise, RFC 7231 [2] disallows sending different response headers for a HEAD than a GET so if the GET for a DLO does not resolve the segments and returns 404, the HEAD must do the same.
There is a note here [3] that segments must be sync'd as well as manifests [3], but it could be clearer that the source and target container names must be the same.
[1] http:// developer. openstack. org/api- ref-objectstora ge-v1.html# showObject /tools. ietf.org/ html/rfc7231# section- 4.3.2 docs.openstack. org/developer/ swift/overview_ container_ sync.html
[2] https:/
[3] http://