HTTP status codes (HEAD object)

The table below describes HTTP status codes that can be returned in response to a request to check the existence of an object, object version, or folder. For more information about HTTP status codes and the error codes that can accompany them, see Error codes.

Code Meaning Description
200 OK

The specified object, object version, delete marker, or folder exists.

304 Not Modified

One of these:

The request included an If-None-Match header, and the ETag for the specified object or object version matched a value specified by the header.

The request included an If-Modified-Since header, and the specified object or object version was not modified after the date and time specified by the header.

403 Forbidden

Possible reasons include:

The credentials provided with the request are invalid.

You do not have read permission for the specified bucket or object.

The S3 compatible API is currently disabled for the specified bucket.

404 Not Found

One of these:

The specified object, object version, or folder does not exist.

The specified bucket does not exist.

409 Conflict Possible reasons include that the object data is currently being written to HCP.
412 Precondition Failed

One of these:

The request included an If-Match header, and the ETag for the specified object or object version does not match any of the values specified by the header.

The request included an If-Unmodified-Since header, and the specified object or object version was modified after the date and time specified by the header.

500 Internal Server Error

An internal error occurred.

If this error persists, contact your tenant administrator.

503 Service Unavailable

HCP is temporarily unable to handle the request, probably due to system overload, maintenance, or upgrade. Try the request again, gradually increasing the delay between each successive attempt.

If this error persists, contact your tenant administrator.

© 2015, 2020 Hitachi Vantara LLC. All rights reserved.