HCP Tenant Management Help
The table below describes the headers you can use in a request to complete a multipart upload.
Request header | Description | Required |
---|---|---|
Authorization | See Authentication. | Yes |
Content-Length | Specifies the size, in bytes, of the request body. | Yes |
Content-Type | Specifies the Internet media type of the request body. The only valid values are application/xml and text/xml. | Yes |
Date | See Common request headers. | Date or x-amz-date |
Host | See Common request headers. | Yes |
If-Match |
Specifies a value for comparison with the ETag of the most recent version of the object specified in the request. If the specified value matches the Etag, HCP continues processing the request. If the specified value doesn't match the Etag or the specified object doesn't exist, HCP returns an error response body and does not complete the multipart upload. The value of this header can be any string of one or more characters. |
No |
x-amz-date | See Common request headers. | x-amz-date or Date |
x-hcp-pretty-print |
Optionally, requests that the XML response body be formatted for readability. Valid values are: •true — Format the XML response body for readability. •false — Do not apply any special formatting to the XML response body. The default is false. The values true and false are not case sensitive. |
No |
x-hcp-retention | Specifies the retention value for the object being stored. This value can be a fixed date, an offset, a retention class, or a special value. | No |
x-hcp-retentionhold | Specifies whether the object is on hold. This value can be either true or false. | No |
Trademarks and Legal Disclaimer
© 2015, 2019 Hitachi Vantara Corporation. All rights reserved.