Docs

Torch Object Storage

API Reference

Response Code

This article describes the response status codes and error codes included in the results returned by the server after a request is sent.

Status Code

The server-side status codes and messages returned by the request are shown below.

Status Code	Description
2XX	Request succeeded. The server has returned the data requested by the user.
3XX	For redirect-related requests, the client must take additional actions to complete the request.
4XX	The client's request contains errors, and the server did not perform any creation or modification of data.
5XX	If a server-side error occurs, users will be unable to determine whether their requests were successful.

Error Code

If an error occurs when the client calls the interface, no result data will be returned. You can identify relevant issues based on the error codes and error messages returned by each interface. When an error occurs during invocation, the HTTP request returns a 3XX, 4XX, or 5XX HTTP status code. The returned message body contains specific error codes and error information.

Error Response

When an error occurs, the returned message will contain the following information:

The 3XX, 4XX, or 5XX HTTP status codes corresponding to errors.

The main text or response also contains information about errors. The following error response example demonstrates the structure of response elements common to all REST error responses.

{
"Code" : "NoSuchKey",
"Message" : "The resource you requested does not exist",
"RequestId" : "4442587FB7D0A2F9",
"HostId" : "",
"Resource" : "/bucketName/objectName"
}

The elements of REST error messages and their corresponding meanings are shown in the following table.

Name	Description
Code	The HTTP message return code corresponding to the error response. An error code is a string that uniquely identifies an error condition.
Message	The detailed English description of the specific error in the error response message.
RequestId	The request ID returned in the response can be used for error localization.
HostId	Returns the server-side ID of the message.
Resource	The bucket or object resources related to this error.

Many error responses contain additional structured data to help developers understand and diagnose programming errors. For example, if you send a REST PUT request with a Content-MD5 header whose digest does not match the one computed by the server, you will receive a BadDigest error. Error response information also includes our computed summary and a prompt for the expected summary information. During the development process, you can use this information to diagnose errors.

Error Code Information

After a request is sent to the TOS storage system, if an error occurs, the response body will contain an error code and the corresponding description.

Error Code	Description	HTTP Status Code	Mitigation Measures
PermanentRedirect	The bucket you are attempting to access must use the specified address. Please send all future requests to this address.	301 Moved Permanently	Send a request to the returned redirect address.
WebsiteRedirect	Website request is missing the bucket name.	301 Moved Permanently	Retry after including the bucket name in the request.
TemporaryRedirect	Temporary redirect: When DNS is updated, requests will be redirected to the bucket.	307 Moved Temporarily	Automatic redirection will occur, and requests can also be sent to the redirect address.
CustomDomainAreadyExist	Configured an existing domain.	400 Bad Request	Configuration has already been completed; no further configuration is required.
CustomDomainNotExist	Delete non-existent domains.	400 Bad Request	Not configured or already deleted; no deletion required.
MalformedError	The XML format included in the request is incorrect.	400 Bad Request	Retry using the correct XML format.
MetadataTooLarge	The metadata message header has exceeded the maximum allowed metadata size.	400 Bad Request	Reduce metadata message headers.
MissingSecurityHeader	The request is missing a required header.	400 Bad Request	Provide the necessary header fields.
EntityTooLarge	The size of the uploaded object exceeds the allowed maximum value.	400 Bad Request	Modify the conditions in the Policy for POST uploads or reduce the object size.
EntityTooSmall	The size of the uploaded object exceeds the permitted minimum value.	400 Bad Request	Modify the conditions in the POST upload policy or increase the object size.
BadDigest	The MD5 value provided by the client does not match the MD5 value calculated by the server.	400 Bad Request	Verify whether the MD5 in the header field matches the MD5 calculated from the message body.
IncompleteBody	The request body was not received in full due to network issues or other problems.	400 Bad Request	Re-upload the object.
InvalidArgument	Parameter format error.	400 Bad Request	Modify according to the error messages in the response body.
InvalidBucket	The requested bucket no longer exists.	400 Bad Request	Change the bucket name.
BadDomainName	Illegal domain name.	400 Bad Request	Verify the domain name and use a legal domain name.
BadRequest	Illegal request parameter.	400 Bad Request	Modify according to the prompts in the returned error message body.
InvalidLocationConstraint	The specified Location is invalid or does not exist when creating the bucket.	400 Bad Request	Specify the correct Location when creating a bucket.
InvalidPart	One or more specified segments could not be found. These segments may not have been uploaded, or the specified Entity Tag does not match the segment's Entity Tag.	400 Bad Request	Merge segments based on the correct segment and Entity Tag.
PartSizeSmall	Merging segments smaller than the specified standard is prohibited, except for the last segment.	400 Bad Request	Update segments that do not meet specifications.
InvalidPartOrder	Invalid segment order. The paragraph list must be arranged in ascending order by paragraph number.	400 Bad Request	After sorting by paragraph number in ascending order, recombine.
IllegalLocationConstraintException	Create a bucket in a non-default region without specifying the Location parameter.	400 Bad Request	Requests are sent to create a bucket in the default Region or to create a bucket with a Location specifying a non-default Region.
InvalidRedirectLocation	Invalid redirect address.	400 Bad Request	Specify the correct address according to the message prompt in the response body.
InvalidRequest	Invalid request.	400 Bad Request	Modify according to the prompts provided in the returned error message body.
InvalidRequestBody	The request body is invalid; a request that requires a message body did not include one.	400 Bad Request	Upload the message body in the correct format.
InvalidTargetBucketForLogging	There is an invalid target bucket in the Logging operation.	400 Bad Request	Retry after configuring ACL permissions for the target bucket.
KeyTooLongError	The provided key is too long.	400 Bad Request	Use a shorter Key.
InvalidBucketName	Invalid bucket name: exceeds length limit or contains disallowed special characters.	400 Bad Request	Change the bucket name.
InvalidEncryptionAlgorithmError	Incorrect encryption algorithm. When downloading an SSE-C encrypted object, an incorrect encryption header field is provided, resulting in failure to decrypt.	400 Bad Request	Download the object with the correct encryption header.
MalformedLoggingStatus	The XML format for Logging is incorrect.	400 Bad Request	Retry using the correct XML format.
MalformedPolicy	Bucket Policy check failed.	400 Bad Request	Modify by combining the prompts in the returned error message body with the requirements of the bucket Policy.
MalformedQuotaError	The XML format of Quota is incorrect.	400 Bad Request	Retry using the correct XML format
MalformedXML	This type of error occurs when a user sends an XML with an incorrect format for a configuration item.	400 Bad Request	Retry using the correct XML format.
MaxMessageLengthExceeded	Copy object with request message body.	400 Bad Request	Retry copying objects without the message body.
InvalidPolicyDocument	The content in the form does not match the conditions specified in the policy document.	400 Bad Request	Based on the prompts in the returned error message body, modify the Policy used to construct the form and retry.
MissingRegion	Region information is missing from the request, and the system does not have a default Region.	400 Bad Request	Include Region information in the request.
MissingRequestBodyError	This occurs when a user sends an empty XML document as a request.	400 Bad Request	Provide a correct XML document.
MissingRequiredHeader	The request is missing required header fields.	400 Bad Request	Provide the necessary header fields.
MalformedACLError	The provided XML is incorrectly formatted or does not conform to our required specifications.	400 Bad Request	Retry using the correct XML format.
TooManyBuckets	The number of buckets owned by the user has reached the system limit, and the request is attempting to create a new bucket.	400 Bad Request	Retry after deleting some buckets.
TooManyWrongSignature	Service was denied due to high-frequency erroneous requests.	400 Bad Request	Retry after replacing with the correct Access Key.
UnexpectedContent	The request either requires a message body that the client did not provide, or does not require a message body but the client included one.	400 Bad Request	Retry according to the instructions.
InvalidCallbackArgument	Validation of callback parameters or custom variables failed.	400 Bad Request	Check callback parameter fields, custom variable formats, and whether Header and Query contain duplicate callback parameters or custom variables.
AccessDenied	You do not have the required access permissions.	403 Forbidden	Check whether the configured permissions support the current operation.
InvalidAccessKeyId	Access Key does not exist in the system.	403 Forbidden	Carry the correct Access Key.
RequestTimeTooSkewed	The time of the request differs significantly from the server's current time.	403 Forbidden	Check whether the client time differs significantly from the current time.
SignatureDoesNotMatch	The signature included in the request does not match the signature calculated by the system.	403 Forbidden	Check your Secret Key and signature calculation method.
NoSuchBucket	The specified bucket does not exist.	404 Not Found	Create the bucket before performing any operations.
NoSuchKey	The specified key does not exist.	404 Not Found	Upload the object first.
NoSuchBucketPolicy	Bucket Policy does not exist.	404 Not Found	First, configure the Bucket Policy.
NoSuchUpload	The specified multipart upload does not exist. Upload ID does not exist, or the multi-part upload has already been aborted or completed.	404 Not Found	Use the existing segment or reinitialize the segment.
NoSuchCORSConfiguration	CORS configuration does not exist.	404 Not Found	First, configure CORS.
NoSuchLifecycleConfiguration	No LifeCycle configuration exists.	404 Not Found	First, configure the bucket's LifeCycle.
NoSuchVersion	The Version ID specified in the request does not match any existing versions.	404 Not Found	Use the correct Version ID.
NoSuchWebsiteConfiguration	The requested website does not exist.	404 Not Found	Configure Website first.
MethodNotAllowed	The specified method is not permitted to operate on the requested resource.	405 Method Not Allowed	Method not allowed.
RequestTimeout	The Socket connection between the user and the server did not perform any read or write operations within the timeout period.	408 Request Timeout	Retry after checking your network, or contact technical support.
BucketAlreadyExists	The requested bucket name already exists. The bucket namespace is shared by all users in the system. Please choose a different bucket name and try again.	409 Conflict	Change the bucket name.
BucketNotEmpty	The bucket the user is attempting to delete is not empty.	409 Conflict	Delete the objects in the bucket first, and then delete the bucket.
BucketAlreadyOwnedByYou	The user who initiated this request has already created a bucket with this name and owns the bucket.	409 Conflict	The bucket already exists; there is no need to create it again.
UpdateConflict	Conflict from Concurrent Updates to the Same Key	409 Conflict	Avoid concurrent updates to the same Key, or contact technical support.
MissingContentLength	The Content-Length field in the HTTP message header must be provided.	411 Length Required	Provide the Content-Length header.
PreconditionFailed	At least one of the user-specified prerequisites has not been included.	412 Precondition Failed	Modify according to the "Condition" prompts in the returned message body.
InvalidRange	The Range specified in the request is invalid.	416 Client Requested Range Not Satisfiable	Retry with the correct Range.
ExceedAccountQPSLimit	Exceeded account QPS limit.	429 StatusTooManyRequests	Reduce the total QPS for requests made using this account, or contact technical support.
ExceedAccountRateLimit	The account bandwidth limit has been exceeded.	429 StatusTooManyRequests	Reduce the total bandwidth used for requests made with this account, or contact technical support.
ExceedBucketQPSLimit	Exceeded bucket QPS limit.	429 StatusTooManyRequests	Reduce the QPS of requests to this bucket, or contact technical support.
ExceedBucketRateLimit	Exceeded bucket bandwidth limit.	429 StatusTooManyRequests	Reduce the bandwidth for requests to this bucket, or contact technical support.
InternalError	The system has encountered an internal error. Please try again.	500 Internal Server Error	Please contact technical support.
ServiceNotImplemented	The method specified in the request is not implemented by the server.	501 Not Implemented	Currently not supported. Please contact technical support.
ServiceUnavailable	Server overload or internal error.	503 Service Unavailable	Please wait for a while and try again, or contact technical support.
SlowDown	Please reduce the frequency of your requests.	503 Service Unavailable	Please reduce the request frequency.

Last updated: 2025.10.10 11:19:07