The table below describes HTTP status codes that can be returned in response to a request to upload a part of a multipart upload. For more information about HTTP status codes and the error codes that can accompany them, see Error codes.
Code | Meaning | Description |
---|---|---|
200 | OK |
HCP successfully uploaded the part. |
400 | Bad Request |
Possible reasons include: •The specified part number is not an integer in the range 1 (one) through 10,000. •The value specified by the Content-MD5 header does not match the Base64-encoded MD5 hash of the data HCP received. •The request includes a custom metadata (x-amz-meta-) header. |
403 | Forbidden |
Possible reasons include: •The request specifies anonymous access. Only an authenticated user can upload parts for a multipart upload. •The credentials provided with the request are invalid. •The credentials provided with the request do not match the credentials used to initiate the multipart upload. •You do not have permission to upload parts in the specified bucket. •The S3 compatible API is currently disabled for the specified bucket. |
404 | Not Found |
One of these: •The specified multipart upload does not exist. Either the upload ID is invalid, or the multipart upload was aborted or completed. In the case of completion, if the part being uploaded is a replacement for an existing part, the existing part is used for completing the multipart upload. •The specified bucket does not exist. |
411 | Length Required | Either the request does not include a Content-Length header, or the request includes a Content-Length header with no value. |
413 | Request Entity Too Large | The part you are trying to upload is too big for the amount of space left in the bucket. |
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.