When an Image Processing (IMG) request fails, IMG returns an XML error response containing an error code and a message to help you diagnose the issue.
Error response format
The following is an example error response:
<Error>
<Code>BadRequest</Code>
<Message>Input is not base64 decoding.</Message>
<RequestId>52B155D2D8BD99A15D0005FF</RequestId>
<HostId>userdomain</HostId>
</Error>The response contains the following elements:
| Element | Description |
|---|---|
Code | The error code. |
Message | A detailed description of the error. |
RequestId | A UUID that identifies the failed request. If the problem persists, provide this value to technical support to help locate the cause. |
HostId | The ID used to identify the accessed IMG cluster. |
Error codes
The following table lists error codes returned by IMG.
| Error code | Description | Solution |
|---|---|---|
InvalidArgument | A parameter value is invalid. | HTTP 400 error codes |
BadRequest | The request is malformed. | — |
MissingArgument | A required parameter is missing. | — |
ImageTooLarge | The image size exceeds the limit. | — |
WatermarkError | A watermark processing error occurred. | — |
NotImplemented | Access is denied. | — |
AccessDenied | Access is denied. | HTTP 403 error codes |
SignatureDoesNotMatch | The request signature does not match the signature calculated by OSS. | — |
NoSuchKey | The specified image does not exist. | HTTP 404 error codes |
NoSuchStyle | The specified style does not exist. | — |
InternalError | An internal error occurred. | HTTP 500 error codes |