Purging 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 purged all versions of the object.

400 Bad Request

The request specified a conditional header, such as If-Match.

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 object is under retention, and you do not have the privileged permission.

The user doesn’t have permission to perform the requested operation.

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 a directory, object, or version 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.

Any component of the URL except for the last component in the path is a symbolic link to a directory.

409 Conflict

HCP could not purge the specified object because it is currently being written to the namespace.

Trademark and LegalDisclaimer

© 2016 Hitachi Data Systems Corporation. All rights reserved.