GetObjectMeta method
Returns object metadata.
The method is equivalent to get, but the object itself is not included in the response.
Request
HEAD /{bucket}/{key} HTTP/2
Path parameters
| Parameter | Description |
|---|---|
bucket |
Bucket name. |
key |
Object key. |
Headers
Use the necessary common request headers in requests.
You can also use the following headers in requests:
| Header | Description |
|---|---|
Range |
Sets the byte range to be uploaded from the object. For more information about the Range header, see the HTTP specification http://www.w3.org/Protocols/rfc2616/rfc2616-sec14.html#sec14.35. |
If-Modified-Since |
If specified, Object Storage returns: - Object. If it has been modified since the specified time. - Code 304. If the object hasn't been modified since the specified time. If a request has both the If-Modified-Since and If-None-Match headers and their checks result in If-Modified-Since -> true and If-None-Match -> false, then Object Storage returns a 304 code. For more information, see RFC 7232. |
If-Unmodified-Since |
If specified, Object Storage returns: - Object. If it has not been modified since the specified time. - Code 412. If the object hasn't been modified since the specified time. If a request has both the If-Unmodified-Since and If-Match headers and their checks result in If-Unmodified-Since -> false and If-Match -> true, then Object Storage returns a 200 code and the requested data. For more information, see RFC 7232. |
If-Match |
If specified, Object Storage returns: - Object. If its ETag matches the one sent.- Code 412. If its ETag doesn't match the one sent one.If a request has both the If-Unmodified-Since and If-Match headers and their checks result in If-Unmodified-Since -> false and If-Match -> true, then Object Storage returns a 200 code and the requested data. For more information, see RFC 7232. |
If-None-Match |
If specified, Object Storage returns: - Object. If its ETag matches the one sent.- Code 304. If its ETag matches the one sent.If a request has both the If-Modified-Since and If-None-Match headers and their checks result in If-Modified-Since -> true and If-None-Match -> false, then Object Storage returns a 304 code. For more information, see RFC 7232. |
Response
Headers
In addition to common response headers, you can see in a response the headers listed in the table below.
| Header | Description |
|---|---|
X-Amz-Meta-* |
Object user-defined metadata. |
X-Amz-Storage-Class |
Object storage class. Has the COLD value if the object is in cold storage, or ICE if in ice storage.If the object is stored in standard storage, there's no header. |
X-Amz-Server-Side-Encryption |
Encryption algorithm used to encrypt the object. Returned if the object was loaded with enabled encryption. |
X-Amz-Server-Side-Encryption-Aws-Kms-Key-Id |
KMS key ID. Returned if the object was loaded with enabled encryption. |
X-Amz-Object-Lock-Mode |
Type of retention put on the object (if the bucket is versioned and object lock is enabled in it):
On an object version, you can put only retention (the headers |
X-Amz-Object-Lock-Retain-Until-Date |
Date and time until which the object is retained, specified in any format described in the HTTP standard. For example, Mon, 12 Dec 2022 09:00:00 GMT. Specified only together with the X-Amz-Object-Lock-Mode header. |
X-Amz-Object-Lock-Legal-Hold |
Type of legal hold put on the object (if the bucket is versioned and object lock is enabled in it):
On an object version, you can put only retention (the headers |
Response codes
For a list of possible responses, see Responses.