First, the HTTP method
Method name |
Description |
Get |
Sends a FETCH request, and the server responds with a head and body section |
Post |
Sends a request for input data, and the server responds with a head and body section |
Head |
The server responds with only the head part |
Put |
Send a file (resource) to the server |
Trace |
In response to the request, the destination server will bring the original request message in the main body, for the client to compare the changes of the data with the firewall, proxy, gateway, etc. |
Options |
Request server informs the Web server of supported features |
Delete |
Requesting the server to delete the resource specified by the URL |
Second, HTTP common status code 1. 100~199 Information Status Code
Status code |
Description |
101 Switching protocols |
For protocol switching, the upgrade response header is implemented, and the server switches to the specified protocol after the upgrade response is sent out. such as: http1.0 upgrade to http1.1 and so on. |
2.200~299成 Function Status Code
Status code |
Description |
Ok |
The request was successful and the desired response header and data body are returned with this response |
201 Created |
The request has been accepted and the new resource has been established (to the handler) based on the requested requirement. |
202 Accepted |
The request has been accepted by the server but has not yet been processed, and the Response 202 status code is here to allow the client to send additional requests. |
203 non-authoritative Information |
The server successfully processes the request, but the returned entity header meta-information is not from a valid determined collection on the original server, but from a local or third-party copy. The current information may be a subset or a superset of the original version |
204 No Content |
Request processing complete, response only to entity header, no entity content, client can not reset view |
205 Reset Content |
Consistent with 204 response, but requires client reset response view |
206 Partial content |
A partial response, a breakpoint continuation, or a large file chunk pass is the response header |
3.300 ~ 399 REDIRECT Status code
Status code |
Description |
Multiple Choices |
The requested resource has a selection of feedback information, redirected based on the header meta-information |
301 Moved Permanently |
Permanent redirect, redirect URL at the location that should be in the head of the response, if no redirect URL should be included in the response body, or if it is not a get and head request, the browser will disallow redirection unless the user acknowledges; http/1.0 sends a POST request. The response is 301, and the next redirect becomes a GET request |
302 Move temporarily |
Temporary redirect, other with 3,011 samples. But Cache-control or expires headers can be cached |
303 See other |
The current request is on another URL, and the client should not cache with get,303, the second request can; http/1.1 processing 303 is consistent with 302 (most browsers) |
304 Not modified |
The client sends a conditional GET request that returns 304 for the cache |
305 Use Proxy |
The specified resource is on the specified proxy, and the location contains the URL of the proxy |
307 Temporary redirect |
With 3,021 |
4.400~499 Error Status Code
status Code /td> |
description |
400 bad Requr EST |
The client sent an incorrect request |
|
requires clients to authenticate themselves before accessing this resource |
|
description request rejected by the server, this class generally does not want to explain why |
404 not found |
Resource not found |
405 method n OT allowed |
The requested method that is sent is not supported by the service-side resource, and the response should include allow header |
|
clients can specify what resources they are willing to accept if the server cannot provide a return of this status code |
5.500~599 Status Code
Status code |
Description |
Internal server Error |
Server Internal Error |
501 Not implemented |
Client requests exceeding the capabilities of the server (e.g., the server cannot support client-requested methods) |
502 Bad Gateway |
The server that the Acting proxy gateway uses receives a pseudo-response from the next link on the request response (for example, it cannot connect to the parent's gateway) |
503 Service Unavailable |
The server is now unable to complete the requested processing, but will |
505 HTTP Version not supported |
The server does not support this Protocol version |
HTTP protocol Status Code summary