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

In this article, the editor introduces in detail "what is the status code of the ajax request". The content is detailed, the steps are clear, and the details are handled properly. I hope that this article "what is the status code of the ajax request" can help you solve your doubts.

The status codes of the ajax request are: 100,101 (switching protocol), 200,2011,205,205,301,400 (error request), 401 (unauthorized), 403 (prohibited), 500 (server internal error), 502 (error gateway) and so on.

The operating environment of this tutorial: windows7 system, javascript1.8.5 version, Dell G3 computer.

Detailed explanation of all status codes requested by ajax

1XX (temporary response):

Indicates a status code that is temporarily corresponding and requires the requester to continue to perform the operation

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

101 (switching protocol): request this request to switch the protocol, and the server has confirmed and is really switched.

2XX (successful):

Status code indicating that the request was processed successfully

200 (successful): the server has successfully processed the request. Typically, this means that the server provides the requested web page. If this status code is displayed for your robots.txt file, Googlebot has successfully retrieved the file.

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 successfully processed the request, but the information returned may have come from another source.

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

205 (reset content): the server successfully processed the request but did not return anything. Unlike the 204 response, this response requires the requestor to reset the document view (for example, clear the form content to enter new content).

Part of the content: the server successfully processed some GET requests.

3xx (redirect)

Further action is required to complete the request. Typically, these status codes are used for redirection. Google recommends that you use redirects no more than 5 times per request. You can use the webmaster tool to see if Googlebot is having problems crawling redirected pages. The web crawl page under diagnostics lists the URLs that cannot be crawled by Googlebot due to redirection errors.

300 (multiple options): 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.

301 (permanent Mobile): the requested web page 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. You should use this code to tell Googlebot that a web page or Web site has been permanently moved to a new location.

302 (temporary Mobility): the server currently responds to requests from web pages in different locations, but the requester should continue to use the original location to respond to future requests. This code, similar to the 301 code that responds to get and head requests, automatically redirects the requestor to a different location, but it should not be used to tell googlebot that a web page or website has moved, as googlebot continues to crawl and index the original location.

303 (see other locations): the server returns this code when the requester should use separate get requests for different locations to retrieve the response. For all requests outside the head, the server automatically redirects to another location

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; if the web page has not changed since the requestor's last request, the server should be configured to return this response (called the if-modified-Since HTTP header). The server can tell googlebot that the web page has not changed since the last crawl, thereby saving bandwidth and overhead.

305 (use proxy): requesters 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.

Server currently responds to web page requests from different locations, but the requester should continue to respond to future requests using the original location. This code is similar to the code that responds to get and head requests and automatically redirects the requestor to a different location, but should not tell googlebot that a page or website has moved, because googlebot will continue to grab the original location and index.

4xx (request error)

These status codes indicate that the request may have an error and hinder the processing of the server

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

401 (unauthorized): the request requires authentication; for the page requested after login, the server may return a secondary response

403 (prohibited): the server rejects the request. If you see this status code when googlebot attempts to crawl a valid page on a website (you can see this information on the web crawl page diagnosed by the google webmaster tool), it may be that the host of the server denied googlebot access

404 (not found):

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

406 (not accepted): a web page that cannot respond to a request using the request content feature

407 (proxy authorization required): this status code is similar to 401 (unauthorized), but the designated requestor should authorize the use of the agent. If the server returns this response, it also indicates that the requestor should use a proxy

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

409 (conflict): the server conflicts while completing the request. The server must include information about the conflict in the response. The server may return this code when responding to a PUT request that conflicts with the previous request, as well as a list of differences between the two requests

410 (deleted): if the requested resource has been permanently deleted, the server returns this response. This code is similar to the 404 (not found) code, but is sometimes used to replace the 404 code in cases where the resource previously existed but does not exist now. If the resource has been permanently moved, you should use 301 to specify the new location of the resource

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 (request entity is too large): the server cannot process the request because the request entity is too large to handle.

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

415 (unsupported media type): the requested format is not supported by the requested page

416 (request scope does not meet the requirements): if the page cannot provide the requested scope, the server will return this status code

417 (did not meet expectations): the server did not meet the requirements of the expected request header field

5XX (server error)

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

500 (server internal error): the server encountered an error and could not complete the request

501 (not yet implemented): the 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

502 (error gateway): the server receives an invalid response from the upstream server as a gateway or proxy

503 (server unavailable): the server is currently unavailable (due to overload or downtime maintenance). Usually, this is just a temporary state

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

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

After reading this, the article "what is the status code of ajax request" has been introduced. If you want to master the knowledge points of this article, you still need to practice and use it yourself to understand it. If you want to know more about related articles, welcome to follow the industry information channel.

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.