Common HTTP status Code

Common HTTP status Code

Common Status Codes:

http:status200– server successfully returned to Web page

http:status404– The requested page does not exist

http:status503– Service Not available

————————————————————————————————

Http:status 1xx (Temporary response)

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

Detailed Code and Description:

Http:status 100 (Continue)

The requestor should continue to make the request. The server returns this code to indicate that the first part of the request was received and is waiting for the remainder.

Http:status 101 (Switching protocol)

The requestor has asked the server to switch protocols and the server has confirmed and is ready to switch.

——————————————————————————————————

HTTP Status 2xx (Success)

Indicates that the status code of the request was successfully processed;

HTTP Status 200 (success)

The server has successfully processed the request. Typically, this indicates that the server provided the requested Web page.

HTTP Status 201 (created)

The request was successful and the server created a new resource.

HTTP Status 202 (accepted)

The server has accepted the request but has not yet processed it.

HTTP Status 203 (non-authorized information)

The server has successfully processed the request, but the information returned may be from another source.

HTTP Status 204 (no content)

The server successfully processed the request, but did not return any content.

HTTP Status 205 (Reset content)

The server successfully processed the request, but did not return any content.

HTTP Status 206 (partial content)

The server successfully processed a partial GET request.

HTTP Status 3xx (redirected)

This requires further action to complete the request. Typically, these status codes are used for redirection.

——————————————————————————————————

HTTP Status 300 (multiple options)

For requests, the server can perform a variety of operations. The server can select an action based on the requestor (user agent) or provide a list of actions for the requestor to select.

HTTP Status 301 (permanent move)

The requested Web page has been permanently moved to a new location. When the server returns this response (a response to a GET or HEAD request), the requestor is automatically forwarded to the 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.

HTTP Status 302 (Temporary Move)

Server now responds to requests from a Web page in a different location, but the requestor should continue to use the original location to respond to future requests. This code, similar to the 301 code that responds to the GET and HEAD requests, automatically transfers the requestor to a different location, but you should not use this code to tell Googlebot that a Web page or site has moved because Googlebot continues to crawl the original location and index it.

HTTP Status 303 (see other locations)

-A requester should use a separate GET request for different locations to retrieve the response when the server returns this code. For all requests except HEAD, the server automatically goes to a different location.

HTTP Status 304 (not modified)

--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 page has not changed since the requestor last requested it, you should configure the server to return this response (known as the If-modified-since HTTP header). The server can tell Googlebot that the webpage has not changed since the last crawl, thus saving bandwidth and overhead.

HTTP Status 305 (use proxy)

The requestor can only use the proxy to access the requested Web page. If the server returns this response, it also indicates that the requestor should use the proxy.

HTTP Status 307 (use proxy)

Server now responds to requests from a Web page in a different location, but the requestor should continue to use the original location to respond to future requests. This code, like the <a href=answer.py?answer=>301</a> code that responds to the GET and HEAD requests, will automatically move the requestor to a different location, but you should not use this code to tell Googlebot A page or site has moved because Googlebot will continue to crawl the original location and index it.

————————————————————————————————————

HTTP Status 4xx (Request error)

These status codes indicate that the request may have failed and that the server has been prevented from processing.

Detailed Code Description:

HTTP Status 400 (Error request)

The server does not understand the syntax of the request.

HTTP Status 401 (not authorized)

Request requires authentication. The server may return this response for pages that need to log on.

HTTP Status 403 (Forbidden)

Server denied request.

HTTP Status 404 (Not Found)

The requested Web page was not found by the server.

HTTP Status 405 (method Disabled)

Disable the method specified in the request.

HTTP Status 406 (not accepted)

, you cannot use the requested content attribute to respond to a requested Web page.

HTTP Status 407 (requires proxy authorization)

This status code is similar to 401 (unauthorized), but specifies that the requestor should authorize the use of the proxy.

HTTP Status 408 (Request timed out)

A timeout occurred while the server was waiting for a request.

HTTP Status 409 (conflict)

Server, a conflict occurred while completing the request. The server must include information about the conflict in the response.

HTTP Status 410 (Deleted)

-If the requested resource has been permanently deleted, the server returns this response.

HTTP Status 411 (valid length required)

Server does not accept requests that do not contain valid Content-Length header fields.

HTTP Status 412 (Prerequisites not met)

Server does not meet one of the prerequisites set by the requestor in the request.

HTTP Status 413 (Request entity too Large)

Server cannot process the request because the request entity is too large to exceed the processing power of the server.

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

HTTP Status 415 (Unsupported media type)

The requested format is not supported by the requested page.

HTTP Status 416 (Request scope does not meet the requirements)

-If the page cannot provide the requested scope, the server returns this status code.

HTTP Status 417 (expectations not met)

Server does not meet the requirements for the expected Request header field.

———————————————————————————————————

HTTP Status 5xx (server error)

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

Code details and Description:

HTTP Status 500 (server internal error)

Server encountered an error and could not complete the request.

HTTP Status 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.

HTTP Status 502 (Error Gateway)

Server as a gateway or proxy, you receive an invalid response from the upstream server.

HTTP Status 503 (Service Unavailable)

Server is not currently available (due to overloading or downtime maintenance). Typically, this is only a temporary state.

HTTP Status 504 (Gateway timed out)

Server as a gateway or proxy, but does not receive requests from the upstream server in a timely manner.

HTTP Status 505 (HTTP version not supported)

The HTTP protocol version used in the request is not supported by the server.

Common HTTP status Code