Request-specific return codes (DELETE annotations)

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 deleted the annotation.

204 No Content

The specified object does not have the specified annotation.

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 user doesn’t have delete permission.

The object is under retention, and the namespace does not allow deleting custom metadata for objects under retention.

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

The URL path contains a symbolic link to a directory anywhere other than in the last component.

409 Conflict

HCP could not delete the annotation because it is currently being written to the namespace.

Trademarks and Legal Disclaimer

© 2017 Hitachi Data Systems Corporation. All rights reserved.