Status Code and Handling Suggestions

Status Code	Description	Solution
200	The request is successful.	-
301	The requested resource has been assigned a new permanent URI, and the new URI is contained in the response.	-
302	The requested resource resides temporarily under a different URI.	-
304	The requested resource has not been modified. In such a case, there is no need to retransmit the resource since the client still has a previously-downloaded copy.	-
400	The server failed to process the request.	Check whether the request syntax or parameters are correct.
401	A username and password are required for access to the requested page.	Log in to the page first.
403	Access to the requested page is denied.	Check whether access controls such as the referer blacklist or whitelist, IP address blacklist or whitelist, and authentication are configured. For details, see Why Is a 4XX Status Code Returned When I Request Resources from My Acceleration Domain Name?
404	The server failed to find the requested page.	Check whether the origin server is normal, or whether the origin server information and host are correctly configured. Check whether the requested resource exists on the origin server. For details, see Why Is a 4XX Status Code Returned When I Request Resources from My Acceleration Domain Name?
405	The request method is not allowed.	Log in to the CDN console, click the acceleration domain name, click the Advanced Settings tab, add the HTTP header Access-Control-Allow-Methods, and set the header value to the required request method. For details, see Why Is a 4XX Status Code Returned When I Request Resources from My Acceleration Domain Name?
406	The response from the server could not be received by the client.	Check whether the value of the Accept header in the response from the origin server is allowed by the client.
407	Proxy authentication is required before the request is processed.	Check whether special authentication is configured.
408	The request timed out.	Check the request sending logic of the client.
409	The request could not be processed due to a conflict.	A conflict usually occurs during the processing of a PUT request. Check the uploaded file.
416	The requested range is invalid.	Check whether the range requested by the client exceeds the resource size.
499	The client closed the request.	Check the client status or timeout interval.
500	The request failed to be fulfilled because of a service error.	Check whether the origin server is normal. For details, see How Do I Check Whether an Access Fault Is Caused by a CDN PoP or Origin Server?
501	The request failed to be fulfilled because the server does not support the required function.	Check whether the request method of the client is correct.
502	The request failed to be fulfilled because the server received an invalid response from the upstream server.	Check whether the origin server is normal. For details, see Why Is a 5XX Status Code Returned When I Request Resources from My Acceleration Domain Name?
503	The request failed to be fulfilled because the system is temporarily abnormal.	Check whether the origin server is normal.
504	A gateway timed out.	Check whether the origin server is normal or overloaded. For details, see Why Is a 5XX Status Code Returned When I Request Resources from My Acceleration Domain Name?