edit-icon download-icon

Description of custom HTTP status codes of CloudMonitor

Last Updated: Jan 30, 2018

All the 6XX status codes returned during your use of the Site Monitoring feature are custom HTTP status codes of CloudMonitor. Their meanings are listed in the following table:

 

Status code    

     Meaning   
 Notes
 610
 HTTP connection time-out   
  Connection times out when the monitoring site detects your website. Status Code 610 is returned if no response packet is returned within five seconds after CloudMonitor sends an HTTP request. We recommend that you increase the number of retries and enable combined alarm rules to optimize and improve alarming accuracy.
 611 
Site access failed during HTTP detection
Check whether your server blocks the CloudMonitor detection requests. If the firewall is enabled, add the latest IP address of CloudMonitor.
 613
 Resolution by DNS failed
Query of domain name resolution failed. We recommend that you contact your DNS service provider to check whether the domain name resolution is unstable.
 615
 Returned response content does not meet user settings
If you use the GET or POST request method and select the “Match response content” option in advanced settings when creating HTTP site monitoring, Status Code 615 is returned when the matching method does not comply with your settings. 
 631 
 TCP connection failed
 
 650
 Connection time-out during DNS detection
 
 681
 Connection to your site failed during FTP detection
 

 

Common HTTP status codes are described as follows. You can use Ctrl + F for a quick search:

 Status code
Meaning  Notes
 200
 Request completed
Status Codes 2XX indicate that the service is normal.
 3XX  
 
Status Codes 3XX indicate redirection.
 300
 Multiple choices
The server can perform multiple operations based on the request. The server selects one operation to perform based on the user agent, or provides a list of operations for the user agent to choose.
 301
 Moved permanently
The requested webpage has been permanently moved to a new location. When the server returns Status Code 301 (in response to a GET or HEAD request), it automatically redirects the user agent to the new location. You must use this status code to notify Googlebot that a webpage or website has been permanently moved to a new location.
 302
 Moved temporarily
The server returns the response from a webpage in a different location, but the user agent must use the original location for subsequent requests. Similar to Code 301 in response to a GET or HEAD request, this code means that the server automatically redirects the user agent to a different location. 
 303
 See other
The server returns this code when the user agent must send GET requests separately for different locations for response retrieval. The server automatically redirects all the requests, except HEAD requests, to other locations.
 304
Not modified 
The requested webpage has not been modified since the last request. The server does not return the webpage content when returning this code.
 305
Use proxy 
The user agent can access the requested webpage only by proxy. If the server returns this code, it also specifies the proxy that the user agent must use.
 307 
 Temporary redirect
The server returns the response from a webpage in a different location, but the user agent must use the original location for subsequent requests. Similar to Code 301 in response to a GET or HEAD request, this code means that the server automatically redirects the user agent to a different location.
 4XX
 
Client errors 
 400 
 Bad request
The server does not understand the syntax of the request. 
 401
Unauthorized 
Authentication is required for the request. The server may return this code in response to the webpage access request after logon.
 403
Forbidden 
The server rejects the request. 
 404
 Not found
The server cannot find the requested webpage. For example, if the requested webpage does not exist on the server, the server usually returns this code.
 405
 Method not allowed
The method specified in the request is forbidden.
 406
 Not acceptable
The content characteristics of the request cannot be used to respond to the webpage access request.
 407
 Proxy authentication required
This status code is similar to 401 (unauthorized), but it specifies that the user agent must use a proxy for authentication. If the server returns this code, it also specifies the proxy that the user agent must use.
 408
 Request time-out
The server timed out waiting for the request.
 409
 Conflict
A conflict occurred when the server completed the request. The server must include the conflict information in the response packet. The server may return this code and provide a list of differences between two conflicting requests when responding to the PUT request that conflicted with the previous request.
 410
 Gone
The server returns this code if the requested resource has been permanently deleted. This code is similar to 404 (not found), but sometimes the server returns 410 instead of 404 if the requested resource that existed before has been deleted.
 411 
 Length required
The server does not accept the request that contains header fields of invalid content length.
 412
 Precondition failed
The server does not meet one of the preconditions that the user agent sets in the request.
 413
 Request entity too large
The server cannot process the request because the request entity is too large and exceeds the server’s processing capability.
 414
 Requested URI too long
The server cannot process the request because the requested URI (usually the URL of the target website) is too long.
 415
 Unsupported media type
The request format is not supported by the requested webpage. 
 416
 Range not satisfiable
The server returns this code if the request is out of the valid range of the requested webpage.
 417
 Expectation failed
The server does not meet the requirements of the Expect request-header field.
 499Client closed requestThis status code is returned when the client closes the connection because it takes a long time for the server to process the request.
 5XX
 
Server errors
 500
 Internal server error
The request cannot be completed due to a server error.
 501
 Not implemented
This code is returned when the server does not have the function to complete the request. For example, when the server cannot identify the request method, it may return this status code.
 502
 Bad gateway
The gateway or proxy server receives an invalid response from the upstream server.
 503
 Service unavailable
The server is currently unavailable (due to overload or shutdown for maintenance). The unavailable state is temporary.
 504
 Gateway time-out
The gateway or proxy server failed to receive requests from the upstream server in time.
 505
 HTTP version not supported
The server does not support the HTTP version in the request. 

 

 

Thank you! We've received your feedback.