HTTP status codes (POST bucket delete objects)

The table below describes HTTP status codes that can be returned in response to a request to delete multiple objects. For more information about HTTP status codes and the error codes that can accompany them, see Error codes.

Code Meaning Description
200 OK

HCP has accepted the request. This does not mean that every object in the request was successfully deleted.

204 No Content

One of these:

HCP successfully deleted the object.

The specified object does not exist.

The current version of the specified object is a delete marker.

400 Bad Request

Possible reasons include:

The request includes a header that is invalid for the requested operation.

The specified bucket name is invalid.

The specified object name is invalid.

403 Forbidden

Possible reasons include:

The credentials provided with the request are invalid.

You do not have delete permission for the specified object.

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

404 Not Found

Possible reasons include that the specified object does not exist.

409 Conflict

Possible reasons include:

The object data is currently being written to HCP.

The specified object is under retention.

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.