Description of custom HTTP status codes of cloudmonitor and custom statuses of cloudmonitor

Description of custom HTTP status codes of cloudmonitor and custom statuses of cloudmonitor

When you use site monitoring, the returned 6XX status codes are all custom HTTP status codes of cloudmonitor. The meanings are shown in the following table:

Status Code	Description	Remarks
610	HTTP connection timeout	Connection times out when the monitoring site detects your website. If no response packet is returned within 5 seconds after cloudmonitor sends an Http request, status code 610 is returned. We recommend that you increase the number of trials and use combined alarms when setting alarm rules to optimize and improve alarm accuracy.
611	HTTP Detection fails to access your site	Check whether your server limits cloudmonitor detection requests. If you have enabled the firewall, add the latest cloudmonitor IP address.
613	DNS cannot be resolved	An error occurred while querying domain name resolution. We recommend that you contact your domain name resolution service provider to check whether domain name resolution is unstable.
615	The returned response content does not match the expectation set by the user.	When you create an HTTP site for monitoring, if you use the GET or POST Request Method and enter "Match response content" in advanced settings ", if the matching method does not match your settings, the 615 status code is returned.
631	TCP Connection Failed
650	DNS detection connection timeout
681	FTP detection fails to connect to your site

Common HTTP status codes are described as follows. You can press ctrl + F to quickly find them:

Status Code	Description	Remarks
200	Request completed	2XX status codes are normal status codes and return
3XX		3XX status code is a redirection status code
300	Multiple options	The server can perform multiple operations based on the request. The server selects an operation based on the User agent or provides an operation list for the User agent to select.
301	Permanent Movement	The requested webpage has been permanently moved to a new location. When the server returns this response (as a response to a GET or HEAD request), it automatically redirects the requester to a new location. You should use this code to notify Googlebot that a webpage or website has been permanently moved to a new location.
302	Temporary Movement	The server is currently responding to requests from different web pages, but the requester should continue to use the original location for future requests. Similar to code 301 In response to GET and HEAD requests, this code automatically redirects the requester to a different location.
303	View other locations	The server returns this code when the requester must perform separate GET requests at different locations to retrieve the response. For all requests except HEAD requests, the server will automatically go to other locations
304	Not modified	The requested webpage has not been modified since the last request. When the server returns this response, no webpage content is returned.
305	Use proxy	The requester can only use a proxy to access the requested webpage. If the server returns this response, the server also specifies the proxy that the requester should use.
307	Temporary redirection	The server is currently responding to requests from different web pages, but the requester should continue to use the original location for future requests. Similar to code 301 In response to GET and HEAD requests, this code automatically redirects the requester to a different location.
4XX		Client errors
400	Error request	The server does not understand the request syntax
401	Unauthorized	The request requires authentication. After login, the server may return this response to the page
403	Disabled	The server rejects the request.
404	Not found	The server cannot find the requested webpage. For example, if the request is for a webpage that does not exist on the server, the server usually returns this code
405	Method disabled	Disable the method specified in the request
406	Not accepted	Unable to use the Content features of the request to respond to the requested webpage
407	Proxy authorization required	This status code is similar to 401 (unauthorized), but specifies that the requester should use a proxy for authorization. If the server returns this response, the server also specifies the proxy that the requester should use.
408	Request timeout	Timeout when the server waits for a request
409	Conflict	A conflict occurs when the server completes the request. The server must contain information about conflicts in the response. The server may return this code in response to a PUT request that conflicts with the previous request, and provide a list of differences between the two requests.
410	Deleted	If the requested resource has been permanently deleted, the server returns this response. This code is similar to the 404 (not found) code, but sometimes it is replaced when the resource exists before but does not exist now
411	Valid length required	The server will not accept requests that contain invalid Content Length header fields.
412	Prerequisites not met	The server does not meet one of the prerequisites set by the requester in the request.
413	The Request Entity is too large.	The server cannot process the request because the request entity is too large and exceeds the server's processing capability.
414	The requested URI is too long.	The request URI (usually the URL) is too long and cannot be processed by the server.
415	Unsupported media type	The request format is not supported by the request page.
416	The request range does not meet the requirements.	If the request is for an invalid webpage range, the server returns this status code.
417	Expectations not met	The server does not meet the "expected" request header field requirements.
499	Client disconnected	Server processing time is too long, causing the client to close the connection
5XX		Server errors
500	Internal Server Error	The request cannot be completed due to a server error.
501	Not Implemented	The server does not have the function to complete the request. For example, if the server cannot identify the request method, the server may return this code.
502	Error Gateway	The gateway or proxy server receives an invalid response from the upstream server.
503	Service unavailable	Currently, servers cannot be used (due to overload or downtime maintenance ). This is usually a temporary state.
504	Gateway timeout	As a gateway or proxy, the server does not receive requests from the upstream server in a timely manner.
505	The HTTP version is not supported.	The server does not support the HTTP protocol version used in the request.