Retrieving an object or multiple versions of an object request-specific return codes

The table below describes the HTTP return codes that have specific meaning for this request. For descriptions of all possible return codes, see HTTP return codes.

Code Meaning Description
200 OK

HCP successfully retrieved a complete object or version.

This code is also returned if the URL specified a valid directory path and HCP returned a directory listing.

204

No Content

The requested version is a deleted version.

206

Partial Content

HCP successfully retrieved the data in the byte range specified in the request.

304

Not Modified

One of:

The request specified an If-None-Match header, and the ETag of the requested object or version matches the value in the header.

The request specified an If-Modified-Since header, and the object change time is at or before the time specified in the header.

400

Bad Request

The request was not valid. These are some, but not all, of the possible reasons:

The URL in the request is not well-formed.

The request has both a type=whole-object query parameter and a Range request header.

The requested object is larger than 512,000 bytes and does not yet have an ETag, and the request included an If-Match or If-None-Match header that did not specify a forceEtag=true query parameter,

The URL in the request is not well-formed.

The request contains an unsupported query parameter or an invalid value for a query parameter.

If more information about the error is available, the response headers include the HCP-specific X‑HCP-ErrorMessage header.

403

Forbidden

The requested operation is not allowed. These are some, but not all, of the possible reasons:

The Authorization header or hcp-ns-auth cookie specifies invalid credentials.

The namespace requires client authentication, and the request does not have an Authorization header or hcp-ns-auth cookie.

The user doesn’t have read permission.

The namespace does not exist.

The access method (HTTP or HTTPS) is disabled.

If more information about the error is available, the response headers include the HCP-specific X‑HCP-ErrorMessage header.

404

Not Found

One of:

HCP could not find an object, version, or directory at the specified URL. The specified object or version does not exist, or the request specified the current version of an object that has been deleted.

When retrieving object or version data and an annotation together, the requested object does not have an annotation with the specified name.

406

Not Acceptable

The request has an Accept-Encoding header that does not include gzip or *.

412

Precondition Failed

One of:

The request specified an If-Match header, and the ETag of the requested object or version does not match the value in the header.

The request specified an If-Unmodified-Since header, and the object change time is after the time specified in the header.

416

Requested Range Not Satisfiable

One of:

The specified start position is greater than the size of the requested data.

The size of the specified range is zero.

503

Service Unavailable

The request contains the nowait query parameter, and HCP determined that the request would have taken a significant amount of time to return the object.

Trademark and LegalDisclaimer

© 2015 Hitachi Data Systems Corporation. All rights reserved.