Error Codes

Last updated: 2021-01-07 15:17:14

    Overview

    This document describes the error codes and corresponding error messages returned when a request fails.

    Error Response

    Content-Type: application/xml

    Corresponding HTTP status code: 3XX, 4XX, or 5XX. Please note that for the PUT Object - Copy API, even if the HTTP status code is 200, the response body may still include an error.

    Response body

    <?xml version='1.0' encoding='utf-8' ?>
    <Error>
                <Code>string</Code>
                <Message>string</Message>
                <Resource>string</Resource>
                <RequestId>string</RequestId>
                <TraceId>string</TraceId>
    </Error>

    The nodes are described as follows:

    Node Name (Keyword) Parent Node Description Type
    Error None Contains all error messages Container

    Content of the Container node Error:

    Node Name (Keyword) Parent Node Description Type
    Code Error Error code, a unique identifier to locate the error conditions and scenario. The error codes are described in detail below string
    Message Error Specific error message string
    Resource Error Requested resource, which can be a bucket or object URL string
    RequestId Error An ID automatically generated by the server when a request is sent. COS can use it to quickly locate faults string
    TraceId Error An ID automatically generated by the server when a request error occurs. COS can use it to quickly locate faults string

    Error Codes

    4XX errors

    </
    HTTP Status Code Error Code Description
    400 Bad Request ActionAccelerateNotSupported The acceleration endpoint does not support this operation
    400 Bad Request AttachmentFull The number of ACLs and policies has exceeded the upper threshold. For more information, please see Specifications and Limits
    400 Bad Request BadDigest Value of the provided Content-MD5 is not the same as the MD5 hash value the server received
    400 Bad Request BadRquest The parameter is invalid
    400 Bad Request BucketAccelerateNotEnabled The acceleration endpoint is not enabled for the bucket
    400 Bad Request BucketNameTooLong The bucket name is too long. For more information, please see “Naming Conventions” in Bucket Overview
    400 Bad Request BucketVersionNotOpen Versioning is not enabled for the bucket
    400 Bad Request DNSRecordVerifyFailed The DNS record fails to be verified. Please add a CNAME or TXT record. The DNS record takes effect within 10 minutes
    400 Bad Request EntitySizeNotMatch The size of the request body is not the same as that specified in the Content-Length request header
    400 Bad Request EntityTooLarge The size of the uploaded object exceeds the upper threshold. For more information, please see Specifications and Limits
    400 Bad Request EntityTooSmall The size of the uploaded object does not reach the lower threshold. This error is often seen in multipart uploads. For more information, please see Specifications and Limits
    400 Bad Request ExpiredToken The temporary token has expired
    400 Bad Request ImageResolutionExceed The image resolution exceeds the limit, or the animated image contains too many frames
    400 Bad Request ImageTooLarge The image is too large
    400 Bad Request IncompleteBody The size of the request body is smaller than that specified in the Content-Length request header
    400 Bad Request IncorrectNumberOfFilesInPostRequest Only one object can be uploaded in a POST Object request
    400 Bad Request InvalidArgument The argument is invalid. Please check whether the request can take this argument
    400 Bad Request InvalidBucketName The bucket name is invalid. For more information, please see Naming Conventions
    400 Bad Request InvalidCopySource The source for object replication is invalid
    400 Bad Request InvalidDelimiter The delimiter parameter is invalid. It should be one character
    400 Bad Request InvalidDigest The provided value of Content-MD5 is invalid
    400 Bad Request InvalidImageFormat The image format is invalid
    400 Bad Request InvalidImageSource The image source is invalid
    400 Bad Request InvalidLocationConstraint The specified location is invalid
    400 Bad Request InvalidObjectName The object name is invalid. For more information, please see ObjectKey
    400 Bad Request InvalidPart A part for multipart upload is missing
    400 Bad Request InvalidPartOrder The part numbers are not continuous
    400 Bad Request InvalidPicOperations The Pic-Operations request header is invalid
    400 Bad Request InvalidPolicyDocument The policy in the POST Object request is invalid
    400 Bad Request InvalidRegionName The endpoint is invalid. For more information, please see Regions and Access Endpoints
    400 Bad Request InvalidRequest The request is invalid
    400 Bad Request InvalidSHA1Digest The request fails the SHA-1 verification
    400 Bad Request InvalidTag The bucket tag is invalid. For more information, please see Bucket Tag Overview
    400 Bad Request InvalidTargetBucketForLogging The destination bucket for logging is invalid. The destination bucket must be in the same region as the current bucket
    400 Bad Request InvalidUploadStatus If versioning is enabled, you cannot call a JSON API to upload objects. Please use an XML API
    400 Bad Request InvalidURI The URI is invalid
    400 Bad Request InventoryFull The number of inventory jobs has exceeded the upper threshold
    400 Bad Request JsonAPINotSupportOnMAZBucket JSON APIs do not support operations on MAZ buckets. Please use XML APIs
    400 Bad Request KeyTooLong The object key is too long. For more information, please see “ObjectKey” in Object Overview
    400 Bad Request KmsException A Key Management Service (KMS) exception occurs
    400 Bad Request KmsKeyDisabled The provided key is disabled
    400 Bad Request KmsKeyNotExist The provided key does not exist
    400 Bad Request ListPartUploadIdIsEmpty UploadId is empty
    400 Bad Request LoggingConfExists The logging configuration already exists
    400 Bad Request LoggingPrefixInvalid The logging prefix is invalid