| 100 |
Continue |
carry on. The client should continue to make the request |
| 101 |
Switching Protocols |
Switch protocol. The server switches the protocol according to the client's request. Can only switch to more advanced protocols, such as switching to the new HTTP protocol |
| 200 |
OK |
The request was successful. Generally used for GET and POST requests |
| 201 |
Create |
Has been created. Successfully requested and created a new resource |
| 202 |
Accepted |
accepted. The request has been accepted, but has not been processed. |
| 203 |
Non-Authoritative Information |
Non-authorized information. The request is successful, but the returned meta information is not on the original server, but a copy (a copy from a local or a third party) |
| 204 |
No Content |
No content. The server processed successfully. But no content was returned. In the case of not updating the page, it can ensure that the browser continues to display the current document |
| 205 |
Reset Content |
Reset content. The server process is successful, and the client terminal should reset the document view. You can use this return code to clear the browser's form field. |
| 206 |
Partial Content |
Part. The server successfully processed part of the get request. |
| 300 |
Multiple Choices |
multiple choices. The requested resource includes multiple locations, and correspondingly, a list of resource characteristics and addresses can be returned for user terminal selection. |
| 301 |
Moved Permanently |
Move permanently. The requested resource has been permanently moved to the new URI, the returned information will include the new URI, and the browser will automatically be directed to the new URI. Any new requests in the future should use new URIs instead |
| 302 |
Move Temporarily |
Move temporarily. Similar to 301. But the resources are only temporarily moved. The client should continue to use the original URI |
| 303 |
See Other |
View other addresses. Similar to 301. View using GET and POST requests |
| 304 |
Not Modified |
Not modified. The requested resource has not been modified. When the server returns this status code, no resource will be returned. The client usually caches the accessed resources, by providing a header information to indicate that the client wants to return only the resources modified after the specified date |
| 305 |
Use Proxy |
Use a proxy. The requested resource must be accessed through a proxy |
| 306 |
Obsolete |
|
| 307 |
Temporary Redirect |
Temporary redirection. Similar to 302. Redirect using GET request |
| 400 |
Bad Request |
The syntax of the client request is incorrect and the server cannot understand it |
| 401 |
Unauthorized |
The request requires user authentication |
| 402 |
Payment Required |
Reserved for future use |
| 403 |
Forbidden |
The server understands the request of the requesting client, but refuses to execute the request |
| 404 |
Not Found |
The server cannot find the resource (web page) according to the client's request. With this code, the website designer can set a personalized page of "The resource you requested cannot be found" |
| 405 |
Method Not Allowed |
The method in the client request is forbidden |
| 406 |
Not Acceptable |
The server cannot complete the request based on the content characteristics requested by the client |
| 407 |
Proxy Authentication Required |
The request requires the identity authentication of the proxy, similar to 401, but the requester should use the proxy for authorization |
| 408 |
Request Timeout |
The server waited too long for the request sent by the client and timed out |
| 409 |
Conflict |
The server may return this code when it completes the client's PUT request, and a conflict occurred when the server processed the request |
| 410 |
Gone |
The resource requested by the client no longer exists. 410 is different from 404. If the resource has been permanently deleted before, the 410 code can be used. The website designer can specify the new location of the resource through the 301 code |
| 411 |
Length Required |
The server cannot process the request information sent by the client without Content-Length |
| 412 |
Precondition Failed |
The prerequisite of the client request information is wrong |
| 413 |
Request Entity Too Large |
The request was rejected because the requested entity was too large for the server to process. To prevent continuous requests from the client, the server may close the connection. If the server is temporarily unable to process, it will contain a Retry-After response message |
| 414 |
Request-URI Too Long |
请求的URI过长（URI通常为网址），服务器无法处理 |
| 415 |
Unsupported Media Type |
服务器无法处理请求附带的媒体格式 |
| 416 |
Requested Range Not Satisfiable |
客户端请求的范围无效 |
| 417 |
Expectation Failed |
服务器无法满足Expect的请求头信息 |
| 500 |
Internal Server Error |
服务器内部错误，无法完成请求 |
| 501 |
Not Implemented |
服务器不支持请求的功能，无法完成请求 |
| 502 |
Bad Gateway |
作为网关或者代理工作的服务器尝试执行请求时，从远程服务器接收到了一个无效的响应 |
| 503 |
Service Unavailable |
由于超载或系统维护，服务器暂时无法处理客户的请求。延时的长度可包含在服务器的Retry-After头信息中 |
| 504 |
Gateway Timeout |
充当网关或代理的服务器，未及时从远端服务器获取请求 |
| 505 |
HTTP Version Not Supported |
服务器不支持请求的HTTP协议的版本，无法完成处理 |