HTTP status information, http €? /A> € €? /A> http € €

HTTP status information, http €? /A> € €? /A> http € €

1. 1xx message

This type of Status Code indicates that the request has been accepted and must be processed.

100 Continue

The client should continue sending the request. This temporary response is used to notify the client that some of the requests have been received by the server and have not been rejected. The client should continue to send the remaining parts of the request.
If the request has been completed, ignore this response. The server must send a final response to the client after the request is complete.

101 Switching Protocols

The server understands the client request and notifies the client to use different protocols to complete the request through the Update message header. Similar measures are taken only when a new protocol is switched to another protocol.

102 Procsessing

The extended Status Code indicates that the processing will continue.

2. 2xx successful

This type of Status Code indicates that the request has been successfully received, understood, and accepted by the server.

200 OK

If the request is successful, the desired response header or data body will be returned accordingly.

201 Created

The request has been implemented, and a new resource has been created based on the request needs, and its URL has been returned with the Location header information.

202 Accepted

The server has accepted the request but has not yet processed it. As it may be rejected, the request may or may not be executed.

203 Non-Authoritative Information

The server has successfully processed the request, but the returned object header metadata is not a valid set on the original server, but a copy from a local or a third party.

204 No Content

The server successfully processes the request, but does not need to return any entity content and wants to return the updated metadata. This response does not contain any message body and ends with the first blank line after the message header.

205 Reset Content

The server successfully processes the request and does not return any content. Different from 204, the response that returns this status code requires the requester to reset the document view. This response is mainly used to receive user input,
Reset the form immediately so that the user can start another input. It is also forbidden to contain any message body.

206 Partial Content

The server has successfully processed some GET requests. HTTP download tools such as FlashGet and thunder all use this type of response to achieve resumable upload or split large files into multiple segments for simultaneous download.

207 Multi-Status

The extended Status Code indicates that the subsequent message body is an XML message and may contain a series of independent response codes based on the number of previous subrequests.

3. 3xx redirection

This type of Status Code indicates that the request can be completed only after the client takes further operations. These status codes are usually used for redirection, and subsequent request addresses (redirection targets) are specified in the Location domain of this response.
Only when the method used for subsequent requests is GET or HEAD can the user's browser automatically submit the required subsequent requests without user intervention.
The client should automatically detect infinite loop redirection, otherwise it will cause unnecessary resource consumption at the Double end. The HTTP/1.0 Standard suggests that the browser should not redirect more than five times.

300 Multiple Choices

The requested resource has a series of optional feedback information, each of which has its own specific address and browser-driven deliberation information. The user or browser can choose a preferred address for redirection.
Unless this is a HEAD request, the response should include a Resource feature and address list entity, so that the user or browser can select the most appropriate redirection address from it.

301 Moved Permanently

The requested resource has been permanently moved to a new location. In the future, any reference to this resource should use one of the several Uris returned in this response.

302 Found

The requested resource now temporarily responds to the request from different Uris. As such redirection is temporary, the client should continue to send future requests to the original address.

303 See other

The response corresponding to the current request can be found on another URI, and the client should use the GET method to access that resource. This request cannot be cached.

304 Not Modified

If the client sends a conditional GET request that is allowed and the content of the document has not changed since the last access or according to the request conditions, the server should return this status code.
304 the response cannot contain a message body.

305 Use Proxy

The requested resource can be accessed only through the specified proxy. The specified proxy URI is provided in the Location field. The receiver must send a separate request to access
Resources. Only the original server can create a 305 response.

306 Switch Proxy

The latest specification is obsolete.

307 Temporary Redirect

The requested resource now temporarily responds to the request from different Uris. As such redirection is temporary, the client should continue to send future requests to the original address. Only in Cache-Control or Expires
The response can be cached.

Iv. 4xx

This type of Status Code indicates that an error may occur on the client, which hinders server processing.

400 Bad Request

The current request cannot be understood by the server due to a syntax error. The client should not submit this request again unless it is modified.

401 Unauthorized

The current request requires user authentication.

402 Payment Required

Reserved

403 Forbidden

The server has understood the request but has refused to execute it.

404 Not Found

Request failed. The requested resource is not found on the server.

405 Method Not Allowed

The content characteristics of the requested resource cannot meet the conditions in the Request Header, so the response entity cannot be generated.

407 Proxy Authentication Required

This is similar to the 401 response, except that the client must perform authentication on the proxy server. The Proxy server must return a Proxy-Authenticate for identity inquiry.

408 Request Timeout

Request timeout. The client did not complete sending a request within the waiting time of the server. The client can submit this request at any time without any changes.

409 Conflict

The request cannot be completed because of a conflict with the current status of the requested resource.

410 Gone

The requested resource is no longer available on the server and there is no known forwarding address.

411 Length Required

The server rejects the request without defining the Content-Length header.

412 Precondition Failed

The server fails to meet one or more of the prerequisites in the header field of the verification request.

413 Request Entity Too Large

The server rejects the current request because the size of the physical data submitted by the request exceeds the scope that the server is willing to or can handle.

414 Request-URI Too Long

The length of the request URI exceeds the length that the server can interpret. Therefore, the server rejects the request.

415 Unsupported Media Type

For the current request method and requested resources, the entity submitted in the request is not in the format supported by the server, so the request is rejected.

416 Request Range Not Satisfiable

If the request contains a Range request header, and any data Range specified in the Range does not overlap with the available Range of the current resource, and the request does not define the If-Range request header,
The server should return the 406 status code.

417 Expectation Failed

The expected content specified in the request header cannot be met by the server, or the server is a proxy server, which has obvious evidence that it is on the next node of the current route, the content of CT cannot be satisfied.

418 I'm a teapot

It is a joke, no need to be defined.

421 There are too functions connections from your internet address

The number of connections from the IP address of the current client to the server exceeds the maximum permitted range of the server. Generally, the IP address here refers to the client address seen from the server. The client here is not necessarily an end user.

422 Unprocessable Entity

The request format is correct, but the request cannot be responded due to semantic errors.

423 Locked

The current resource is locked.

424 Failed Dependency

The current request fails due to an error in a previous request.

425 Unordered Collection

Not officially used.

426 Upgraed Required

The client should switch to TLS/1.0.

449 Retry

By Microsoft extension, requests should be retried after appropriate operations are performed.

451 Unavailable For Legal Reasons

Approved by IETF, the access representative is rejected because of legal requirements.

5. 5xx Server Error

This type of Status Code indicates that an error or exception occurs when the server processes the request, or the server may realize that the current hardware and software resources cannot process the request.

500 Internal Server Error

The server encountered an unexpected situation, causing it to fail to process the request. Generally, the error occurs when the program code on the server fails.

501 Not Implemented

The server does not support a function required by the current request. When the server cannot identify the Request Method and cannot support its requests to any resource.

502 Bad Gateway

When a gateway or proxy server tries to execute a request, it receives an invalid response from the upstream server.

503 Service Unavailable

The server cannot process requests because of temporary server maintenance or overload.

504 Gateway Timeout

When a gateway or proxy server tries to execute a request, it fails to receive a response from the upstream server or the secondary server in a timely manner.
Note: Some proxy servers will return error 400 or 500 when DNS lookup times out.

505 HTTP Version Not Supported

The server does not support or rejects the HTTP Version Used in the application. This implies that the server cannot or does not want the same version as the client.

506 Variant Also Negotiates

Extended by the transparent content negotiation protocol, which indicates that the server has an internal configuration error.

507 Insufficient Storage

The server cannot store the content required to complete the request.

509 Bandwidth Limit Exceeded

The server reaches the bandwidth limit. This is not an official status, but it is still widely used.

510 Not Extended

The policies required for obtaining resources are not met.