If a COS request fails when calling this SDK, it will throw a
CosClientException (client exception) or
CosServerException (server exception).
CosClientExceptionresults from unexpected interaction issues between the client and the COS server, such as a failure to connect to the server, a failure to parse the data returned by the server, or the occurrence of an IO exception when reading a local file, etc.
CosServerExceptionoccurs when the client interacts with the COS server normally, but the operation fails. For example, the client accesses a bucket that does not exist, deletes a file that does not exist, or does not have the permission to perform an operation, etc.
CosClientException is used in the same way as
System.ApplicationException. An additional member errorCode is also added, as shown below:
|errorCode||Client error code, such as 10000, which indicates a parameter verification failure. For more information, see Error Codes||int|
CosServiceException contains the status code returned by the server, the
requestid, and the error details. After an exception is captured, we recommended that you print out the entire exception as it contains necessary factors for troubleshooting. The member variables of the exception are described as follows:
|requestId||Request ID, used to identify a request. It is very important for troubleshooting.||string|
|statusCode||Status code in the response. A
|errorCode||Error code returned by the body when the request fails. For more information, see Error Codes.||string|
|errorMessage||Error message returned by the body when the request fails. For more information, see Error Codes.||string|
COS provides a self-help diagnosis tool to help you quickly locate request problems and debug code.
RequestId) returned when the request error occurs.
RequestIdand click Diagnose.