Responses

Successful response
If there are no errors, ColdStack responds with 2xx HTTP codes. The response code and body depend on the request and are discussed in the request descriptions.
Error response
When an error occurs, ColdStack responds with a message with the appropriate HTTP code and optional XML description.
1
<?xml version="1.0" encoding="UTF-8"?>
2
<Error>
3
  <Code>NoSuchKey</Code>
4
  <Message>The resource you requested does not exist</Message>
5
  <Resource>/mybucket/myfoto.jpg</Resource>
6
  <RequestId>4442587FB7D0A2F9</RequestId>
7
</Error>
Copied!
Tag
Description
Code
Error code.

See the list of codes below in the text.
Message
Description of the error in English.
RequestId
The identifier of the request that caused the error.

Equal to the value of the title x-amz-request-id.
Resource
The bucket or object that encountered an error.
Error codes
HTTP
Error code
Description
301
PermanentRedirect
The specified bucket should always be addressed to the address indicated in the response.
307
Redirect
The specified bucket should be temporarily addressed at the address indicated in the response.
307
TemporaryRedirect
Redirect for the duration of the DNS update.
400
BadDigest
The hash passed in the header Content-MD5does not match the one calculated on the ColdStack side.
400
CredentialsNotSupported
Credentials are not supported.
400
EntityTooSmall
The loaded object is less than the minimum size allowed.
400
EntityTooLarge
The loaded object is larger than the maximum allowed.
400
ExpiredToken
The provided token has expired.
400
IncompleteBody
The size of the sent data is smaller than indicated in the header Content-Length.
400
IncorrectNumberOfFilesInPostRequest
The POST method requires the transfer of exactly one file.
400
InlineDataTooLarge
The request data exceeded the maximum size allowed.
400
InvalidDigest
The hash passed in the Content-MD5 header is not correct.
400
InvalidArgument
Invalid argument.
400
InvalidBucketName
Invalid bucket name.
400
InvalidPart
One or more parts of the composite load were not found. Check the list is correct. Possibly missing parts were not loaded.
400
InvalidPartOrder
The list of parts for a composite load is incorrect. Parts must be sorted in ascending order.
400
InvalidRequest
Use AWS4-HMAC-SHA256.
400
InvalidRequest
An attempt was made to exceed the maximum bucket size.

Error description in response: "You have attempted to exceed the max size configured for the bucket."
400
InvalidStorageClass
Invalid storage class.

Common response headers

Last modified 9mo ago

Copy link

Contents

Successful response

Error response