Storing 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
201 Created

HCP successfully stored the object. If versioning is enabled and an object with the same name already exists, HCP created a new version of the object.

304

Not Modified

A request to store a new version of an existing object specified an If-Modified-Since header, and the change time of the current version is at or before the time specified in the header.

400

Bad Request

One of:

The URL in the request is not well-formed.

The request has a Content-Encoding header that specifies gzip, but the data is not in gzip-compressed format.

The request has a type=whole-object query parameter, and either:

oThe request does not have an X-HCP-Size header.

oThe X-HCP-Size header value is greater than the content length.

The namespace has custom metadata XML checking enabled, and the request included an annotation that is not well-formed XML.

If the request that causes this error contains both object data and an annotation, HCP creates an empty object before it returns the error. To resolve this issue, you can either:

oFix the annotation and retry the request.

oStore the object again without the annotation, thereby replacing the empty object. You can then fix the annotation at a later time and add it in a separate request.

A request to store a version of an existing object included an If-Match or If-None-Match header and the object does not yet have an ETag.

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

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

403

Forbidden

One of:

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 write permission.

For a request to store a version of an existing object, the object is under retention.

The namespace does not exist.

The access method (HTTP or HTTPS) is disabled.

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

409

Conflict

One of:

HCP could not store the object in the namespace because the object already exists and versioning is not enabled.

HCP could not store a new version of an existing object because another version is currently being added.

HCP could not evaluate conditional headers because a version of the object is currently being added.

412

Precondition Failed

One of:

A request to store a new version of an object specified an If-Match header, and the ETag of the existing object does not match the value in the header.

A request to store a new version of an existing object specified an If-None-Match header, and the ETag of the existing object matches the value in the header.

A request to store a new version of an existing object specified an If-Unmodified-Since header, and the change time of the existing object is after the time specified in the header.

413

File Too Large

One of:

Not enough space is available to store the object. Try the request again after objects or versions are deleted from the namespace or the namespace capacity is increased.

The request is trying to store an object that is larger than two TB. HCP cannot store objects larger than two TB.

The request is trying to store custom metadata that is larger than one GB. HCP cannot store custom metadata larger than one GB.

415

Unsupported Media Type

The request has a Content-Encoding header with a value other than gzip.

Trademark and LegalDisclaimer

© 2015 Hitachi Data Systems Corporation. All rights reserved.