Show object metadata

head

/v1/{account}/{container}/{object}

Shows object metadata.

Request

Path Parameters
  • The unique name for the account. An account is also known as the project or tenant.
  • The unique name for the container. The container name must be from 1 to 256 characters long and can start with any character and contain any pattern. Character set must be UTF-8. The container name cannot contain a slash (/) character because this character delimits the container and object name. For example, /account/container/object.
  • The unique name for the object.
Query Parameters
  • Minimum Value: 0
    The date and time in UNIX Epoch time stamp format when the signature for temporary URLs expires.

    For example, 1440619048 is equivalent to Mon, Wed, 26 Aug 2015 19:57:28 GMT.

  • Used with temporary URLs to sign the request with an HMAC-SHA1 cryptographic signature that defines the allowed HTTP method, expiration date, full path to the object, and the secret key for the temporary URL.
Header Parameters
  • Authentication token. Not specified if temp_url_sig and temp_url_expires are present. Otherwise, if you omit this header, your request fails unless the account owner has granted you access through an access control list (ACL).
  • If set to true, Object Storage queries all replicas to return the most recent one. If you omit this header, Object Storage responds faster after it finds one valid replica. Because setting this header to true is more expensive for the back end, use it only when it is absolutely needed.
Back to Top

Response

Supported Media Types

200 Response

Success
Headers
  • (Optional) If set, specifies the override behavior for the browser. For example, this header might specify that the browser use a download program to save this file rather than show the file, which is the default.

    If not set, this header is not returned by this operation.

  • (Optional) If set, the value of the Content-Encoding metadata.

    If not set, the operation does not return this header.

  • Minimum Value: 0
    HEAD operations do not return content. The Content-Length header value is not the size of the response body but is the size of the object, in bytes.
  • The MIME type of the object.
  • The transaction date and time.

    The date and time stamp format is ISO 8601:

    CCYY-MM-DDThh:mm:ss±hh:mm
    For example, 2015-08-27T09:49:58-05:00.

    The ±hh:mm value, if included, is the time zone as an offset from UTC. In the previous example, the offset value is -05:00.

    A null value indicates that the token never expires.

  • For objects smaller than 5 GB, this value is the MD5 checksum of the object content. The value is not quoted.

    For manifest objects, this value is the MD5 checksum of the concatenated string of MD5 checksums and ETags for each of the segments in the manifest, and not the MD5 checksum of the content that was downloaded. Also the value is enclosed in double-quote characters.

    You are strongly recommended to compute the MD5 checksum of the response body as it is received and compare this value with the one in the ETag header. If they differ, the content was corrupted, so retry the operation.

  • The date and time when the object was created or its metadata was changed.

    The date and time stamp format is ISO 8601:

    CCYY-MM-DDThh:mm:ss±hh:mm
    For example, 2015-08-27T09:49:58-05:00.

    The ±hh:mm value, if included, is the time zone as an offset from UTC. In the previous example, the offset value is -05:00.

  • The time when the restored object is scheduled to expire. Note that this header is only returned for fully-restored objects.
  • State of the archived object
    Allowed Values: [ "Archived", "Restored", "InProgress" ]
  • Tracking URL provided if status is Archived or InProgress.

    URL will be of the form http://{storage_url}/v1/{account}/{container}?jobs&jobId={restore_jobid}

  • Minimum Value: 0
    (Optional) If set, the date and time in UNIX Epoch time stamp format when the system deletes the object.

    For example, 1440619048 is equivalent to Mon, Wed, 26 Aug 2015 19:57:28 GMT.

    If not set, this operation does not return this header.

  • (Optional) If set, to this is a dynamic large object manifest object. The value is the container and object name prefix of the segment objects in the form container/prefix.
  • The custom object metadata item, where {name} is the name of the metadata item.

    One X-Object-Meta-{name} response header appears for each metadata {name} item.

  • Set to True if this object is a static large object manifest object.
  • Minimum Value: 0
    The date and time in UNIX Epoch time stamp format when the account, container, or object was initially created as a current version.

    For example, 1440619048 is equivalent to Mon, Wed, 26 Aug 2015 19:57:28 GMT.

  • A unique transaction ID for this request. Your service provider might need this value if you report a problem.
  • Minimum Value: 0
    (Optional) The Epoch time that an uploaded object must exist until it can be deleted. The value will be greater than the current Epoch time.

401 Response

Request does not include an authentication token, or authentication token specified in the request is not valid. It may have expired. Authentication tokens expire after 30 minutes.
Headers

403 Response

Forbidden. Possible causes:
  • A data center has not been selected for your service in Oracle Cloud My Services.
  • The request was sent to an incorrect data center. For example, the data center for your service is Chicago (us2), but the request was sent to the URL corresponding to the Ashburn (us6) data center.
  • You don't have the required permission to perform the operation on the specified container. For example, there may be a change in the roles assigned to your user or the access privileges defined for the container specified in the request.
  • The specified operation is not permitted for archive objects or containers with storage class Archive
  • Violating a container or object level WORM policy by trying to PUT, POST, or DELETE an object that has not expired or trying to update an existing container level WORM policy.
Headers

404 Response

The object does not exist or has just been created and hasn't been replicated across all three nodes.
Headers
Back to Top

Examples

cURL Command

The following example shows how to retrieve information about an object in a container in your account in Oracle Cloud Infrastructure Object Storage Classic by submitting a HEAD request on the REST resource using cURL. For more information about cURL, see Use cURL.

curl -v -X HEAD \
     -H "X-Auth-Token: AUTH_tkb4fdf39c92e9f62cca9b7c196f8b6e6b" \
     https://foo.storage.oraclecloud.com/v1/myservice-bar/FirstContainer/myObject

Sample Response

The following is a sample response of this command:

HTTP/1.1 200 OK
Accept-Ranges: bytes
Last-Modified: Wed, 16 Dec 2015 08:14:17 GMT
Etag: f1c9645dbc14efddc7d8a322685f26eb
X-Timestamp: 1450253656.45313
Date: Thu, 28 Jan 2016 08:56:32 GMT
Content-Length: 10485760
Content-Type: application/octet-stream;charset=UTF-8
X-Trans-Id: tx23a1084b8c674fdeae8d4-0054f982ac
X-Last-Modified-Timestamp: 1450253656.45313
Back to Top