HTTP Status Codes

HTTP Status Codes

This status code provides information about the status of the request and provides Googlebot with information about your site and the requested page.

Some common status codes are:

  • 200 - The server successfully returned the web page
  • 404 - The requested page does not exist
  • 503 - Server Temporarily Unavailable

A complete list of HTTP status codes is provided below. Click the link for more information. You can also visit the W3C page on HTTP status codes for more information .

1xx (Provisional Response)
A status code used to indicate a provisional response that requires action by the requester before continuing.

Code illustrate
100 (Continued) Requesters should continue to make requests. When the server returns this code, it means that the server has received the first part of the request and is now waiting to receive the rest.
101 (Switching Protocol) The requester has asked the server to switch protocols, and the server has acknowledged and is ready to make the switch.

2xx (Successful)

A status code that indicates that the server successfully processed the request.

Code illustrate
200 (Success) The server successfully processed the request. Typically, this means that the server provided the requested web page. If your robots.txt file shows this status, it means that Googlebot has successfully retrieved the file.
201 (Created) The request was successful and the server created the new resource.
202 (Accepted) The server has accepted the request but has not yet processed it.
203 (Unauthorized Message) The server successfully processed the request but returned information that might have come from another origin.
204 (No Content) The server successfully processed the request but did not return any content.
205 (Reset content) The server successfully processed the request but did not return any content. Unlike the 204 response, this response requires the requester to reset the document view (for example, clear the form contents to enter new content).
206 (partial content) The server successfully processed a partial GET request.

3xx (Redirected)
To complete your request, you need to take further action. Typically, these status codes are forever redirects. Google recommends that you use fewer than 5 redirects per request. You can use Webmaster Tools to see if Googlebot has trouble crawling your redirected pages. The Crawl Errors page under Diagnostics lists URLs that Googlebot couldn't crawl due to redirect errors.

Code illustrate
300 (multiple choices) The server can perform various operations based on the request. The server can select an operation based on the requester (User agent) or provide a list of operations for the requester to choose from.
301 (Moved Permanently) The requested page has been permanently moved to a new location. When the server returns this response (in response to a GET or HEAD request), it automatically forwards the requester to the new location. You should use this code to notify Googlebot that a page or site has been permanently moved to a new location.
302 (Moved Temporarily) The server is currently responding to requests from a web page at a different location, but the requester should continue to use the original location for future requests. This code is similar to the 301 code in response to GET and HEAD requests, and automatically redirects the requester to a different location. However, because Googlebot will continue to crawl and index the old location, you should not use this code to notify Googlebot that a page or site has moved.
303 (see other locations) The server returns this code when the requester should make separate GET requests to different locations to retrieve the response. For all requests except HEAD requests, the server automatically forwards to another location.
304 (Not Modified)

The requested page has not been modified since the last request. When the server returns this response, no web page content is returned.

You should configure your server to return this response (called the If-Modified-Since HTTP header) if the web page has not changed since the requester last requested it. This saves bandwidth and overhead because the server can tell Googlebot that the page has not changed since the last crawl.

.
305 (Use Proxy) The requester can only access the requested web page using a proxy. If the server returns this response, the server also indicates the proxy that the requester should use.
307 (Temporary Redirect) The server is currently responding to requests from a web page at a different location, but the requester should continue to use the original location for future requests. This code is similar to the 301 code in response to GET and HEAD requests, and automatically redirects the requester to a different location. However, because Googlebot will continue to crawl and index the old location, you should not use this code to notify Googlebot that a page or site has moved.

4xx (Bad Request)
These status codes indicate that something might have gone wrong with the request, which prevented the server from processing the request.

Code illustrate
400 (Bad Request) The server did not understand the syntax of the request.
401 (Unauthorized) The request requires authentication. After logging in, the server might return this response to the page.
403 (Forbidden) The server rejected the request. If this status code appears when Googlebot tries to crawl a valid page on your site (you can see this status code on the Web Crawl page under Diagnostics in Google Webmaster Tools), it's possible that your server or host is denying Googlebot access to it.
404 (Not Found)

The server could not find the requested webpage. For example, a server would typically return this code if the request was for a page that didn't exist on the server.

If you do not have a robots.txt file on your site and you see this status on the robots.txt page in the Diagnostics tab of Google Webmaster Tools, then this is the correct status. However, if you have a robots.txt file and see this status, your robots.txt file may be named incorrectly or located in the wrong location. (The file should be located on the top-level domain and should be named robots.txt).

If you see this status on a URL that Googlebot is trying to crawl (on the HTTP error page of the Diagnostics tab), it means that Googlebot may be following a broken link on another page (either an old link or a link that was typed incorrectly).

405 (Method Forbidden) Disables the method specified in the request.
406 (Not Accepted) The requested web page could not be responded to with the requested content attributes.
407 (Proxy Authorization Required) This status code is similar to 401 (Unauthorized), but specifies that the requester should use a proxy for authorization. If the server returns this response, the server also indicates the proxy that the requester should use.
408 (Request Timeout) The server timed out while waiting for the request.
409 (Conflict) The server encountered a conflict while completing the request. The server MUST include information about the conflict that occurred in the response. A server may return this code in response to a PUT request that conflicts with a previous request, along with a list of the differences between the two requests.
410 (Deleted) The server returns this response if the requested resource has been permanently deleted. This code is similar to the 404 (Not Found) code, but is sometimes used instead of the 404 code when a resource previously existed but no longer exists. If the resource has been permanently deleted, you should use the 301 code to specify the new location of the resource.
411 (Valid Length Required) The server will not accept a request containing an invalid Content-Length header field.
412 (Precondition Not Met) The server did not meet one of the preconditions set by the requester in the request.
413 (Request Entity Too Large) The server cannot process the request because the request entity is too large to handle.
414 (Requested URI Too Long) The requested URI (usually a URL) is too long for the server to process.
415 (Unsupported Media Type) The requested format is not supported by the requested page.
416 (Requested range does not meet requirements) The server returns this status code if the request is made to an invalid range for the page.
417 (Expectations not met) The server did not meet the requirements of an 'Expect' request-header field.

5xx (Server Error)
These status codes mean that an internal error occurred while the server was trying to process the request. These errors may be errors with the server itself, rather than errors with the request.

Code illustrate
500 (Internal Server Error) The server encountered an error and could not complete the request.
501 (Not yet implemented) The server does not have the functionality to fulfill the request. For example, a server might return this code when the server does not recognize the request method.
502 (Bad Gateway) The server, acting as a gateway or proxy, received an invalid response from an upstream server.
503 (Service Unavailable) The server is currently unavailable (either because it is overloaded or down for maintenance). Usually, this is only a temporary condition.
504 (Gateway Timeout) The server, acting as a gateway or proxy, did not receive a request from the upstream server in a timely manner.
505 (HTTP Version Not Supported) The server does not support the HTTP protocol version used in the request.

HTTP return code list (Chinese and English explanation)

http return code list (below is an overview) for detailed Chinese explanation please click here
1** Reserved
100 : Continue
101: witching Protocols
2** Indicates that the request was successfully received
200 : OK
201 : Created
202 : Accepted
203 : Non-Authoritative Information
204 : No Content
205 : Reset Content
206 : Partial Content
3** To complete the request, the customer needs to further refine the request
300 : Multiple Choices
301 : Moved Permanently
302 : Found
303 : See Other
304 : Not Modified
305 : Use Proxy
307 : Temporary Redirect
4** Customer Error
400 : Bad Request
401 : Unauthorized
402 : Payment Required
403 : Forbidden
404 : Not Found
405 : Method Not Allowed
406 : Not Acceptable
407 : Proxy Authentication Required
408 : Request Time-out
409 : Conflict
410 : Gone
411 : Length Required
412 : Precondition Failed
413 : Request Entity Too Large
414 : Request-URI Too Large
415 : Unsupported Media Type
416 : Requested range not satisfied
417 : Expectation Failed
5** Server Error
500 : Internal Server Error
501 : Not Implemented
502 : Bad Gateway
503 : Service Unavailable
504 : Gateway Time-out
505 : HTTP Version not supported
_____________________________________________________________________
HTTP return code Chinese explanation
2xx Crawl OK
200 OK; the request was completed. (Generally this state
201 OK; immediately following a POST command.
202 OK; accepted for processing, but processing is not yet complete.
203 OK; Partial Information - The information returned is only partial.
204 OK; No Response — The request was received, but there is no information to send back.
3xx Redirect
301 Permanent Redirect — The requested data has a new location and the change is permanent.
302 Temporary Redirect — The requested data temporarily has a different URI.
303 See Other - The response to the request can be found under another URI and should be retrieved using the GET method.
304 Not Modified — The document was not modified as expected.
305 Use Proxy - The requested resource must be accessed through the proxy provided in the Location field.
306 Unused — No longer used; this code is reserved for future use.
4xx Page Error
400 Bad Request — There was a syntax problem in the request, or the request could not be fulfilled.
401 Unauthorized — The client is not authorized to access the data.
402 Payment Required — Indicates that the billing system is active.
403 Forbidden — Access is not required even if authorized.
404 Not Found — The server could not find the given resource; the document does not exist.
406 Not Acceptable - The resource identified by this request can only generate response entities whose content is characterized as "Not Acceptable" according to the "Accept" headers sent in this request.
407 Proxy-Authorization-Request - The client must first authenticate itself with the proxy.
410 The requested page does not exist (permanent);
415 UnsupportedMediaType - The server is refusing to service the request because the format of the request entity is not supported.
5xx Server Error
500 Internal Error — The server could not complete the request due to an unexpected condition.
501 Not Implemented — The server does not support the requested tool.
502 Bad Gateway — The server received an invalid response from an upstream server.
503 Service Unavailable — The server is unable to process the request due to a temporary overload or maintenance.
100 Continue
Indicates that the client should continue with the request. The loopback is used to notify the client that the request has been received and has not been rejected by the server.
The client SHOULD continue to send the rest of the request data or the request is complete, or ignore the echo data. The server MUST send a final echo after the request.
101 Switching Protocols
The server changes the application protocol of the current connection through the Upgrade header information according to the client's request. The server will immediately change the protocol based on the Upgrade header when the 101 response ends with a blank line.
Successful
=================================
200 OK
Indicates that the client's request has been successfully received, parsed, and accepted.
201 Created
The request has been completed and a new response resource has been created. The resource being created may be a URI resource, which is usually specified in the Location header. The response should contain an entity data and include the resource characteristics and location through the appropriate method selected by the user or user agent. The entity data format is specified by the body type, namely the content-type header. Initially the server must create the specified resource before returning a 201 status code. If the action is not taken immediately, the server SHOULD return 202.
202 Accepted
The request has been accepted for processing. But the processing is not complete. The request may or may not be followed at all, as the processing may actually be denied.
203 Non-Authoritative Information
204 No Content
The server has accepted the request and does not necessarily return entity data, but may need to return updated information. The response may contain new or updated information represented by entity-headers.
205 Reset Content
The server has accepted the request and the user agent should reset the document view.
206 Partial Content
The server has accepted the request for a GET request for a resource. The request must include a Range header to indicate the range to retrieve and may include an If-Range header to make the request conditional.
Redirection
==================================
300 Multiple Choices
Requests resources that match any one of the representation modes.
301 Moved Permanently - The resource being redirected has been assigned a new URI.
302 Found
Request a temporary file for a resource with a different URI.
303 See Other
304 Not Modified
If the client has completed a conditional request and the request is allowed, but the document has not changed, the server SHOULD return a 304 status code. 304
The status code MUST NOT contain a message body, which is usually terminated by the first empty line after a header field.
305 Use Proxy
The requested resource must be accessed through a proxy (specified by the Location field). The Location resource gives the URI of the proxy.
306 Unused
307 Temporary Redirect
Client Error
=====================
400 Bad Request
The server could not understand the request due to incorrect syntax.
401 Unauthorized
If the request requires user authentication. The response SHOULD include a WWW-Authenticate header field indicating the authority to request the resource.
402 Payment Required
Reserved status code
403 Forbidden
The server accepted the request, but refused to process it.
404 Not Found
The server has found any resource matching the Request-URI.
405 Menthod Not Allowed
The requested method in the Request-Line is not allowed by the specified URI.
406 Not Acceptable
407 Proxy Authentication Required
408 Request Timeout
The client did not submit any request within the server's waiting time.
409 Conflict
410 Gone
411 Length Required
The server refuses to accept the request if the Content-Length field is not defined.
412 Precondition Failed
413 Request Entity Too Large
The server is refusing to process the request because the request data exceeds what the server can process. The server may close the current connection to prevent the client from making further requests.
414 Request-URI Too Long
The server is refusing to service the current request because the length of the URI exceeds the server's parsing range.
415 Unsupported Media Type
The server is refusing to service the current request because the request data format is not supported by the requested resource.
416 Request Range Not Satisfied
417 Expectation Failed
Server Error
===================================
500 Internal Server Error
The server encountered an exception that prevented the execution of the current request
501 Not Implemented
The server has no corresponding execution action to complete the current request.
502 Bad Gateway
503 Service Unavailable
The server cannot process the current request because of temporary file overload.
504 Gateway Timeout
505 Http Version Not Supported

<<:  Detailed explanation of downloading, installing and using nginx server

>>:  The difference between html form submission action and url jump to actiond

Recommend

Problems and solutions of using jsx syntax in React-vscode

Problem Description After installing the plugin E...

...

How to install openssh from source code in centos 7

Environment: CentOS 7.1.1503 Minimum Installation...

Teach you to create custom hooks in react

1. What are custom hooks Logic reuse Simply put, ...

Detailed analysis of javascript data proxy and events

Table of contents Data Brokers and Events Review ...

Reasons and solutions for slow MySQL query stuck in sending data

Because I wrote a Python program and intensively ...

In-depth understanding of Vue transition and animation

1. When inserting, updating, or removing DOM elem...

Solution to the failure of entering the container due to full docker space

Since the problem occurred rather suddenly and th...

Vue implements weather forecast function

This article shares the specific code of Vue to r...

Talking about Less and More in Web Design (Picture)

Less is More is a catchphrase for many designers....

mysql calculation function details

Table of contents 2. Field concatenation 2. Give ...

Discussion on the Issues of Image Button Submission and Form Repeated Submission

In many cases, in order to beautify the form, the ...

Analysis of the reasons why the index does not take effect when searching in the MySql range

1 Problem Description This article sorts the esta...

Vue implements dynamic routing details

Table of contents 1. Front-end control 1. In the ...

Detailed explanation of the process of building and running Docker containers

Simply pull the image, create a container and run...