Shulou(Shulou.com)06/02 Report--

This article mainly introduces what status codes are in HTTP, which can be used for reference by interested friends. I hope you can learn a lot after reading this article.

Detailed status description key

300: the requested resource has a range of feedback information to choose from, each with its own specific address and browser-driven negotiation information. Users or browsers can choose a preferred address for redirection.

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

The requested resources are now temporarily responding to requests from different URI. Because such redirects are temporary, the client should continue to send future requests to the original address.

The response to the current request can be found on another URI, and the client should access that resource in a GET manner. This method exists primarily to allow POST request output activated by the script to be redirected to a new resource. This new URI is not a substitute reference to the original resource. At the same time, the 303 response is prohibited from being cached.

304If the client sends a conditional GET request and the request is allowed, and the content of the document (since the last access or according to the requested condition) has not changed, the server should return this status code.

305: the requested resource must be accessed through the specified agent. The URI information of the specified agent is given in the Location domain, and the receiver needs to send a separate request repeatedly to access the corresponding resources through this proxy. Only the original server can create a 305 response.

306: in the latest version of the specification, the 306 status code is no longer used.

The requested resources are now temporarily responding to requests from different URI. Because such redirects are temporary, the client should continue to send future requests to the original address.

There are more than other status codes.

Semantic error, the current request cannot be understood by the server. The client should not submit this request repeatedly unless it is modified. 2. The request parameters are incorrect.

401: the current request requires user authentication. The response must contain a WWW-Authenticate header for the requested resource to ask for user information. The client can repeatedly submit a request containing the appropriate Authorization header information. If the current request already contains Authorization certificates, the 401 response means that the server verifies that those certificates have been rejected. If the 401 response contains the same authentication challenge as the previous response, and the browser has attempted authentication at least once, the browser should show the user the entity information contained in the response. because this entity information may contain relevant diagnostic information.

402: this status code is reserved for possible future requirements.

403: the server understands the request but refuses to execute it. Unlike the 401 response, authentication does not provide any help, and the request should not be submitted repeatedly.

404: the request failed and the desired resource was not found on the server. There is no information to tell the user whether the situation is temporary or permanent.

405: the request method specified in the request line cannot be used to request the corresponding resource. The response must return an Allow header to indicate a list of request methods that are acceptable to the current resource.

406: the content characteristics of the requested resource cannot meet the conditions in the request header, so the response entity cannot be generated.

407: similar to the 401 response, except that the client must authenticate on the proxy server.

408: request timed out. The client does not complete the sending of a request within the time that the server prepares to wait. The client can resubmit the request at any time without making any changes.

409: the request cannot be completed due to a conflict with the current state of the requested resource.

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

411: the server refuses to accept requests without defining Content-Length headers. After adding a valid Content-Length header indicating the length of the request message, the client can submit the request again.

412: when the server verifies that the prerequisites are given in the header field of the request, one or more of them are not satisfied.

413: the server refuses to process the current request because the physical data submitted by the request is larger than the server is willing or able to handle.

414: the URI length of the request exceeds the length that the server can interpret, so the server refuses to service the request.

415: for the currently requested method and the requested resource, the entity submitted in the request is not in a supported format on the server, so the request is rejected.

416: if the request contains a Range request header, and any data range specified in Range does not coincide with the available range of the current resource, and there is no If-Range request header defined in the request, the server should return a 416 status code.

417: the expected content specified in the request header Expect cannot be satisfied by the server, or the server is a proxy server, which has clear evidence that the content of Expect cannot be satisfied on the next node of the current route.

421: the number of connections from the current client's IP address to the server exceeds the maximum permitted by the server.

423: the request is in the correct format, but cannot respond because it contains semantic errors.

424: the current request failed due to an error in a previous request, such as PROPPATCH.

425: defined in the WebDavAdvancedCollections draft but not in the WebDAV Sequential set Protocol (RFC3658).

The client should switch to TLS/1.0.

449: extended by Microsoft to represent the request that it should be retried after the appropriate action has been performed.

Thank you for reading this article carefully. I hope the article "what status codes are in HTTP" shared by the editor will be helpful to you. At the same time, I also hope you will support us and pay attention to the industry information channel. More related knowledge is waiting for you to learn!

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.