The content size of the body in bytes.
The base-64 encoded MD5 hash of the body, as described in RFC 2616, section 14.15. Unavailable for objects uploaded using multipart upload. If the {@code content-md5} header is present, Object Storage performs an integrity check on the body of the HTTP request by computing the MD5 hash for the body and comparing it to the MD5 hash supplied in the header. If the two hashes do not match, the object is rejected and an HTTP-400 Unmatched Content MD5 error is returned with the message: "The computed MD5 of the request body (ACTUAL_MD5) does not match the Content-MD5 header (HEADER_MD5)"
For optimistic concurrency control. See ETags for Optimistic Concurrency Control.
The artifact modification time, as described in RFC 2616, section 14.29.
Unique Oracle assigned identifier for the request. If you need to contact Oracle about a particular request, then provide the request ID.
The returned stream.Readable | ReadableStream instance.
The content disposition of the body, as described in RFC 2616, section 19.5.1.