The table below describes the headers you can use in a request to store an object.
Request header | Description | Required |
---|---|---|
Authorization | See Authentication. | Yes |
Content-Length | Specifies the size, in bytes, of the data being stored. | Yes |
Content-MD5 | Directs HCP to check the integrity of the data it receives by comparing a Base64-encoded MD5 hash of that data to the value specified by this header. The valid value for this header is the Base64-encoded MD5 hash of the data in the request body. | No |
Content-Type | Specifies the Internet media type of the data being stored. Valid values are Internet media types (for example, text/plain, application/xml, or image/jpeg). | No |
Date | See Common request headers. | Date or x-amz-date |
Expect | Tells the application not to send the request body if the request headers are rejected. The only valid value is 100-continue. This value is not case sensitive. | No |
Host | See Common request headers. | Yes |
x-amz-acl |
Adds a canned ACL to the object. This header is used only to add a canned ACL to an object. If you’re using individual x-amz-grant- headers to add the ACL, the x-amz-acl header is invalid. For valid values for this header, see Canned ACLs. |
No |
x-amz-date | See Common request headers. | x-amz-date or Date |
x-amz-grant-full- control |
Grants full control over the object to one or more specified grantees. If you’re using a canned ACL to add an ACL to an object, the x-amz-grant-full-control header is invalid. For valid values for this and the following x-amz-grant- headers, see Specifying an ACL with headers. |
No |
x-amz-grant-read |
Grants the browse and read data access permissions for the object to one or more specified grantees. If you’re using a canned ACL to add an ACL to an object, the x-amz-grant-read header is invalid. |
No |
x-amz-grant-read-acp |
Grants the read ACL data access permission for the object to one or more specified grantees. If you’re using a canned ACL to add an ACL to an object, the x-amz-grant-read-acp header is invalid. |
No |
x-amz-grant-write |
Grants the write and delete data access permissions for the object to one or more specified grantees. If you’re using a canned ACL to add an ACL to an object, the x-amz-grant-write header is invalid. |
No |
x-amz-grant-write-acp |
Grants the write ACL data access permission for the object to one or more specified grantees. If you’re using a canned ACL to add an ACL to an object, the x-amz-grant-write-acp header is invalid. |
No |
x-amz-meta- |
Adds custom metadata to the object. For information about using this header, see Storing custom metadata with the S3 compatible API. |
No |
x-amz-server-side- encryption |
Requests that the response headers include x-amz-server-side-encryption, which indicates whether objects stored in HCP are encrypted. The value of the x-amz-server-side-encryption request header can be any character string. | 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 |
© 2015, 2020 Hitachi Vantara LLC. All rights reserved.