HTTP status Code

Summary of current status codes:

1, 2XX success

The corresponding result of 2XX indicates that the request has been processed properly.

1.1 OK

Indicates that a request from the client is handled properly on the server side

1.2 204 No Content

Indicates that the request received by the server has been processed successfully, but does not contain the contents of the entity in the returned response message

1.3 206 Partial Content

Indicates that the client made a scope request, and the server successfully performed this part of the GET request. The response message contains the entity content specified by the Content-range range

2, 3XX redirect 2.1 301 Moved Permanently

Permanent redirection. White Oh Name The requested resource has been assigned a new URI, and the URI that the resource now refers to should be used later. That is, if you have already saved the URI of the resource as a tag, you should save it by the URI of the Location header field prompt.

2.2 302 Found

Temporary redirection. Indicates that the requested resource has been assigned a new URI and that the user (this time) can use the new URI to access

2.3 303 See other

Indicates that the requested resource should be directed to a request by using the Get method because this other URI exists for the corresponding resource.

When the 301 302 303 Response Status code returns, almost all browsers change the post to get and delete the principal within the request message, and the request is sent again automatically. 301 302 Standard is to prohibit the post method to be changed to get method, but in actual use everybody will do so

2.4 304 Not Modified

Indicates that when a client sends a request with a condition, the server allows the request to access the resource but does not meet the condition. 304 When the status code returns, does not contain the body part of any response

2.5 307 Temporary Redirect

Temporary redirection, the status code has the same meaning as 302. Although the 302 standard prohibits post from being converted to get, it is not observed when actually used. 307 will comply with browser standards and will not change from post to get, but for the behavior of handling responses, there may be different scenarios for each browser

3.4XX Client Error

4XX response results indicate that the client is the cause of the error

3.1 Bad Request

Indicates that there is a syntax error in the request message, and when the error occurs, you need to modify the requested content and send the request again. In addition, the browser will treat the status code as if it were

3.2 401 Unauthorized

Indicates that the request sent requires authentication information that is authenticated by HTTP and that the user authentication fails if the previous 1 requests have been made

The response that returns 401 must contain a www-authenticate header that applies to the requested resource to challenge the user information. When the browser first receives a 401 response, it pops up the authentication dialog window

3.3 403 Forbidden

Indicates that access to the requested resource was rejected by the server

3.4 404 Not Found

Indicates that the requested resource could not be found on the server. In addition, you can use it when the server rejects the request and does not want to explain the reason

4.5XX Server Error

5XX response results indicate that the server itself has an error

4.1 Internal Server Error

Indicates that an error occurred while the server was executing the request. It may also be a bug or some temporary failure in the web App

4.2 503 Service Unavailable

Indicates that the server is temporarily overloaded or is under maintenance and cannot process requests now

HTTP status Code