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

This article mainly introduces "how to understand the status code in the HTTP protocol". In the daily operation, I believe that many people have doubts about how to understand the status code in the HTTP protocol. The editor consulted all kinds of materials and sorted out the simple and easy-to-use operation methods. I hope it will be helpful to answer the doubts about "how to understand the status code in the HTTP protocol". Next, please follow the editor to study!

A status code that represents a temporary response and requires the requestor to continue with the operation.

Code description

100 (continue) the requestor shall continue to make the request. The server returns this code indicating that the first part of the request has been received and is waiting for the rest.

101 (switching protocol) the requestor has asked the server to switch the protocol, and the server has confirmed and is ready to switch.

2xx (successful)

Indicates the status code that successfully processed the request.

Code description

200 (successful) the server has successfully processed the request. Typically, this means that the server provides the requested web page.

201 (created) the request was successful and the server created a new resource.

202 (accepted) the server has accepted the request, but has not yet processed it.

203 (unauthorized information) the server has successfully processed the request, but the information returned may have come from another source.

The 204 (no content) server successfully processed the request but did not return anything.

The 205 (reset content) server successfully processed the request but did not return anything.

The server successfully processed some GET requests.

3xx (redirect)

Indicates that further action is required to complete the request. Typically, these status codes are used for redirection.

Code description

300 (multiple selections) the server can perform a variety of actions for requests. The server can select an action based on the requestor (user agent), or provide a list of actions for the requestor to choose from.

The web page requested by 301 (permanent Mobile) has been permanently moved to a new location. When the server returns this response (the response to a GET or HEAD request), it automatically moves the requestor to a new location.

The 302 (temporary mobile) server currently responds to requests from web pages in different locations, but the requester should continue to use the original location for future requests.

The server returns this code when the requester should use separate GET requests for different locations to retrieve the response.

304 (unmodified) the requested web page has not been modified since the last request. When the server returns this response, the web page content is not returned.

305 (use proxy) requestors can only use agents to access the requested web page. If the server returns this response, it also indicates that the requestor should use a proxy.

The 307 (temporary redirect) server currently responds to requests from web pages in different locations, but the requester should continue to use the original location for future requests.

4xx (request error)

These status codes indicate that the request may have gone wrong, hindering the processing of the server.

Code description

400 (error request) the server does not understand the syntax of the request.

The 401 (unauthorized) request requires authentication. For web pages that need to log in, the server may return this response.

The 403 (prohibited) server rejected the request.

404 (not found) the server could not find the requested web page.

405 (method disabled) disables the method specified in the request.

406 (not accepted) cannot respond to a requested web page with the requested content feature.

407 (Agent authorization required) this status code is similar to 401 (unauthorized), but the designated requestor should authorize the use of the agent.

408 (request timeout) the server timed out while waiting for a request.

409 (conflict) the server collided while completing the request. The server must include information about the conflict in the response.

410 (deleted) if the requested resource has been permanently deleted, the server returns this response.

411 (valid length required) the server does not accept requests without valid content length header fields.

412 (prerequisites not met) the server did not meet one of the prerequisites set by the requestor in the request.

413 (the request entity is too large) the server cannot process the request because the request entity is too large to handle.

414 (the requested URI is too long) the requested URI (usually the URL) is too long for the server to process.

415 (unsupported media type) the format of the request is not supported by the request page.

416 (request range does not meet requirements) if the page cannot provide the requested scope, the server returns this status code.

417 (did not meet expectations) the server did not meet the requirements of the expectation request header field.

5xx (server error)

These status codes indicate that an internal error occurred while the server was trying to process the request. These errors may be the fault of the server itself, not the request error.

Code description

500 (server internal error) the server encountered an error and was unable to complete the request.

The 501 (not yet implemented) server does not have the ability to complete the request. For example, this code may be returned when the server does not recognize the request method.

The 502 (error gateway) server, as a gateway or proxy, received an invalid response from the upstream server.

The 503 (service unavailable) server is currently unavailable (due to overload or downtime maintenance). Usually, this is only a temporary state.

The 504 (gateway timeout) server acts as a gateway or proxy, but does not receive a request from the upstream server in time.

505 (the HTTP version is not supported) the server does not support the HTTP protocol version used in the request.

At this point, the study on "how to understand the status code in the HTTP protocol" is over. I hope to be able to solve your doubts. The collocation of theory and practice can better help you learn, go and try it! If you want to continue to learn more related knowledge, please continue to follow the website, the editor will continue to work hard to bring you more practical articles!

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.