HTTP Status Code – CSDN blog

Some common status codes are:

200 // The server successfully returned page 404 // The requested page does not exist 503 // The server is unavailableCopy the code

Explanation of all states:

1XX (Interim response)

A status code that represents a temporary response and requires the requester to continue with the operation.

Code instructions

100 // The requester should continue to make the request. The server returns this code to indicate that it has received the first part of the request and is waiting for the rest. 101 // Switch protocol The requester has asked the server to switch protocol, and the server has confirmed and is ready to switch protocol.Copy the code

2XX (Success)

200 // Success The server has successfully processed the request. Typically, this means that the server has provided the requested web page. 202 // Accepted The server has accepted the request, but not yet processed 203 // The unauthorized information server has successfully processed the request, but the information returned may come from another source 204 // No content server has successfully processed the request, 205 // The reset content server successfully processed the request, but did not return any content 206 // Part of the content server successfully processed part of the GET requestCopy the code

3xx (Redirection)

Indicates that further action is required to complete the request. Typically, these status codes are used for redirects.

Code instructions

300 // Multiple options The server can perform multiple operations on a request. The server can select an operation based on the requester (User Agent) or provide a list of operations for the requester to select. 301 // Permanently moved requested page permanently moved to new location. When the server returns this response (a response to a GET or HEAD request), it automatically forwards the requester to the new location. 302 // The temporary mobile server is currently responding to requests from pages in different locations, but the requester should continue to use the original location for future requests 303 // View other locations Requester should use separate GET requests for different locations to retrieve responses when the server returns this code 304 // Not modified automatically after the last request, The requested page has not been modified. The server returns this response, but does not return the content of the page. If the server returns this response, it also means that the requester should use the proxy 307 // to temporarily redirect the server's current response to the web page from a different location, but the requester should continue to use the original location for future requestsCopy the code

4xx (Request error)

400 // The error request server does not understand the syntax of the request 401 // Unauthorized requests require authentication. For pages that require login, The server may return this response 403 // Forbid the server to reject the request 404 // Not found The server could not find the requested page 405 // method Disable Disable the method specified in the request 406 // Do not accept the page that cannot use the requested content feature 407 // Proxy authorization is required This status code is similar to 401 (unauthorized), but specifies that the requester should authorize the use of proxy 408 // Request timeout server timeout occurred while waiting for the request 409 // Conflict Server conflict occurred while completing the request. The server must include information about the conflict in the response. 410 // Deleted If the requested resource has been permanently deleted, The server will return this response 411 // Requires a valid length The server will not accept a request that does not contain a valid content length header field 412 // Does not meet one of the prerequisites set by the requester 413 // Request entity is too large the server cannot process the request because the request entity is too large, 414 // The URI of the request is too long the URI of the request (usually the website) is too long, and the server cannot process it 415 // Unsupported media Type The format of the request is not supported by the requested page 416 // The request scope is invalid If the page cannot provide the requested scope. The server returns this status code 417 // Unmet expectations The server does not meet the requirements of the "expected" request header fieldCopy the code

5xx (Server error)

These status codes indicate that an internal error occurred while the server was trying to process the request. These errors may be server errors rather than request errors.

Code instructions

500 // Internal server error The server encountered an error and could not complete the request 501 // Not yet implemented The server does not have the capability to complete the request. For example, the server may return this code 502 // error when it cannot recognize the request method. The gateway server acted as a gateway or proxy and could not receive an invalid response from the upstream server. 503 // Server unavailable The server is currently unavailable (due to overloading or downtime for maintenance). Usually, this is just a temporary state 504 // Gateway timeout the server acts as a gateway proxy, but did not receive the request from the upstream server in time 505 //HTTP version unsupported The server does not support the HTTP protocol version used in the requestCopy the code