HTTP Status Code List _ Basic Tutorial

Source: Internet
Author: User
Tags ldap rfc

We often encounter 404, 500, 302 and other hints, what do they mean? In addition to these common status codes, what are some of the status codes that we have not encountered but are likely to appear? Here I made a summary, share with you.

HTTP Status Code Summary description
-----------------------------------------------------------------------------------------------------------

Successful 2XX successfully processed the requested status code.
200 the server has successfully processed the request and provided the requested Web page.
204 The server successfully processed the request, but did not return any content.
REDIRECT 3XX use redirection not more than 5 times per request.
301 The requested Web page has been permanently moved to the new location. When URLs change, use 301 code. A new URL is saved in the Search engine index.
302 The requested Web page is temporarily moved to a new location. The original URL is saved in the Search engine index.
304 If the page has not been updated since the request was last requested, use 304 code to tell the search engine robot to save bandwidth and overhead.
The client error 4XX indicates that the request could be wrong, preventing the server from processing.
400 the server does not understand the syntax of the request.
403 The server refused the request.
404 the server could not find the requested Web page. Pages that do not exist on the server often return this code.
The server returns this response after the 410 requested resource has been permanently deleted. The code is similar to the 404 (not Found) code,
However, it is sometimes used to replace the 404 code in cases where the resource existed before and now does not exist. If the resource has been permanently deleted, you should use 301 to specify a new location for the resource.
Server error 5XX indicates that the server encountered an internal error while processing the request. These errors may be errors on the server itself, not the request.
500 the server encountered an error and could not complete the request.
503 Server is currently unavailable (due to overloading or downtime maintenance). Usually, this is only a temporary state.

Detailed decomposition:

2XX success

200 normal; The request is complete.
201 Normal; Immediately following the POST command.
202 normal; Accepted for processing, but processing has not yet completed.
203 normal; Partial information-the information returned is only part of the message.
204 normal; No response-received request, but no information to echo.

3XX redirect

301 Moved-The requested data has a new location and the change is permanent.
302 found-The requested data has a different URI temporarily.
303 See other-you can find a response to a request under another URI, and you should use the Get method to retrieve the response.
304 Not modified-the document is not modified as expected.
305 Use proxy-the requested resource must be accessed through the agent provided in the Location field.
306 unused-is no longer in use, and retains this code for future use.

Error occurred in 4XX client

400 Error request-There is a syntax problem in the request or cannot satisfy the request.
401 not authorized-the client is not authorized to access the data.
402 Payment required-Indicates that the billing system is valid.
403 prohibited-access is not required even with authorization.
404 Not Found-the server cannot find the given resource; The document does not exist.
407 Proxy authentication Request-The client must first use the proxy authentication itself.
415 Media type not supported-server denial of Service request because the format of the request entity is not supported.

Error occurred in 5XX server

500 INTERNAL Error-The server cannot complete the request because of an unexpected condition.
501 not executed-the server does not support the requested tool.
502 Error Gateway-server received an invalid response from the upstream server.
503 cannot get service-the server cannot process the request due to temporary overload or maintenance.

504 Gateway Timeout
When a server working as a gateway or proxy attempts to execute a request, it fails to receive a response from the upstream server (the server identified by the URI, such as HTTP, FTP, LDAP), or a secondary server (for example, DNS) in a timely manner.
Note: Some proxy servers return 400 or 500 errors in DNS query timeout

505 HTTP Version not supported
The server does not support, or the HTTP version used in the request is denied. This implies that the server is unable or unwilling to use the same version as the client. The response should contain an entity that describes why the version is not supported and which protocols the server supports.

506 Variant Also negotiates
Extended by the Transparent Content negotiation Protocol (RFC 2295), which represents an internal configuration error on the server: The requested negotiation meta resource is configured to use itself in transparent content negotiation, so it is not an appropriate focus in a negotiation process.

507 Insufficient Storage
The server cannot store the content required to complete the request. This situation is considered to be temporary. WebDAV (RFC 4918)

508 Loop Detected
An infinite loop occurred in the server discovery request

509 bandwidth Limit exceeded
Server reaches bandwidth limit. This is not an official status code, but it is still widely used.

510 Not Extended
The policies required to get resources are not unsatisfied. (RFC 2774)

How to handle common errors

500 error

500 error is the webmaster often encountered problems, on my experience, reasons and solutions summed up as follows:

1, running too many users, the server caused by too much pressure, the server can not respond, then reported HTTP500 error.

This reason is the website report 500 error Most main reason, many websites why suddenly report 500 error (Service unavailable)? 90% is due to the space pressure is too large, beyond the space quotient set by the ceiling caused.

Encounter this problem, it is best to find the first time space business after-sales service, they will generally help you recycle the application pool, the problem is solved. If you do not find after-sales service, you can own in the space management background, to find the "Recycle application Pool" that project, their own manual execution can be. However, some space management backgrounds do not provide the service.

2. If the possibility of the 1th is ruled out, a big reason is that there are problems in the procedure.

Can do a simple test page to see if it can run successfully, and then detect the error of the page, so targeted to modify.

The place to do the association does not have to do the association, then reported HTTP500 error. The problem is solved by manual or automatic association.

3, if the test in the operation of the need to insert data into the database, if the large amount of data in the case of the table space is full, or buffer pool is not enough to meet the data access, etc., may lead to HTTP500 errors.

The solution is to adjust the database, modify the connection pool size and so on, according to individual specific circumstances to amend.


HTTP Status Code Summary description
-----------------------------------------------------------------------------------------------------------

Successful 2XX successfully processed the requested status code.
200 the server has successfully processed the request and provided the requested Web page.
204 The server successfully processed the request, but did not return any content.
REDIRECT 3XX use redirection not more than 5 times per request.
301 The requested Web page has been permanently moved to the new location. When URLs change, use 301 code. A new URL is saved in the Search engine index.
302 The requested Web page is temporarily moved to a new location. The original URL is saved in the Search engine index.
304 If the page has not been updated since the request was last requested, use 304 code to tell the search engine robot to save bandwidth and overhead.
The client error 4XX indicates that the request could be wrong, preventing the server from processing.
400 the server does not understand the syntax of the request.
403 The server refused the request.
404 the server could not find the requested Web page. Pages that do not exist on the server often return this code.
The server returns this response after the 410 requested resource has been permanently deleted. The code is similar to the 404 (not Found) code,
However, it is sometimes used to replace the 404 code in cases where the resource existed before and now does not exist. If the resource has been permanently deleted, you should use 301 to specify a new location for the resource.
Server error 5XX indicates that the server encountered an internal error while processing the request. These errors may be errors on the server itself, not the request.
500 the server encountered an error and could not complete the request.
503 Server is currently unavailable (due to overloading or downtime maintenance). Usually, this is only a temporary state.

Detailed decomposition:

2XX success

200 normal; The request is complete.
201 Normal; Immediately following the POST command.
202 normal; Accepted for processing, but processing has not yet completed.
203 normal; Partial information-the information returned is only part of the message.
204 normal; No response-received request, but no information to echo.

3XX redirect

301 Moved-The requested data has a new location and the change is permanent.
302 found-The requested data has a different URI temporarily.
303 See other-you can find a response to a request under another URI, and you should use the Get method to retrieve the response.
304 Not modified-the document is not modified as expected.
305 Use proxy-the requested resource must be accessed through the agent provided in the Location field.
306 unused-is no longer in use, and retains this code for future use.

Error occurred in 4XX client

400 Error request-There is a syntax problem in the request or cannot satisfy the request.
401 not authorized-the client is not authorized to access the data.
402 Payment required-Indicates that the billing system is valid.
403 prohibited-access is not required even with authorization.
404 Not Found-the server cannot find the given resource; The document does not exist.
407 Proxy authentication Request-The client must first use the proxy authentication itself.
415 Media type not supported-server denial of Service request because the format of the request entity is not supported.

Error occurred in 5XX server

500 INTERNAL Error-The server cannot complete the request because of an unexpected condition.
501 not executed-the server does not support the requested tool.
502 Error Gateway-server received an invalid response from the upstream server.
503 cannot get service-the server cannot process the request due to temporary overload or maintenance.

504 Gateway Timeout
When a server working as a gateway or proxy attempts to execute a request, it fails to receive a response from the upstream server (the server identified by the URI, such as HTTP, FTP, LDAP), or a secondary server (for example, DNS) in a timely manner.
Note: Some proxy servers return 400 or 500 errors in DNS query timeout

505 HTTP Version not supported
The server does not support, or the HTTP version used in the request is denied. This implies that the server is unable or unwilling to use the same version as the client. The response should contain an entity that describes why the version is not supported and which protocols the server supports.

506 Variant Also negotiates
Extended by the Transparent Content negotiation Protocol (RFC 2295), which represents an internal configuration error on the server: The requested negotiation meta resource is configured to use itself in transparent content negotiation, so it is not an appropriate focus in a negotiation process.

507 Insufficient Storage
The server cannot store the content required to complete the request. This situation is considered to be temporary. WebDAV (RFC 4918)

508 Loop Detected
An infinite loop occurred in the server discovery request

509 bandwidth Limit exceeded
Server reaches bandwidth limit. This is not an official status code, but it is still widely used.

510 Not Extended
The policies required to get resources are not unsatisfied. (RFC 2774)

How to handle common errors

500 error

500 error is the webmaster often encountered problems, on my experience, reasons and solutions summed up as follows:

1, running too many users, the server caused by too much pressure, the server can not respond, then reported HTTP500 error.

This reason is the website report 500 error Most main reason, many websites why suddenly report 500 error (Service unavailable)? 90% is due to the space pressure is too large, beyond the space quotient set by the ceiling caused.

Encounter this problem, it is best to find the first time space business after-sales service, they will generally help you recycle the application pool, the problem is solved. If you do not find after-sales service, you can own in the space management background, to find the "Recycle application Pool" that project, their own manual execution can be. However, some space management backgrounds do not provide the service.

2. If the possibility of the 1th is ruled out, a big reason is that there are problems in the procedure.

Can do a simple test page to see if it can run successfully, and then detect the error of the page, so targeted to modify.

The place to do the association does not have to do the association, then reported HTTP500 error. The problem is solved by manual or automatic association.

3, if the test in the operation of the need to insert data into the database, if the large amount of data in the case of the table space is full, or buffer pool is not enough to meet the data access, etc., may lead to HTTP500 errors.

The solution is to adjust the database, modify the connection pool size and so on, according to individual specific circumstances to amend.



1**: Request received, continue processing
2**: Operation received, analyzed and accepted successfully
3**: Complete this request must be further processed
4**: request contains an error syntax or cannot be completed
5**: Server failed to perform a fully valid request

100--customer must continue to issue a request
101--client requires the server to convert the HTTP protocol version on request

200--Trading Success
201--prompts to know the URL of the new file
202--accept and process, but processing incomplete
203--return information is uncertain or incomplete
204--request received, but return information is empty
The 205--server completes the request and the user agent must reset the files that are currently browsed
The 206--server has completed some of the user's Get requests

300--requested resources can be obtained in multiple places
301--Delete request data
302--found request data at other addresses
303--advises customers to access other URLs or access methods
The 304--client has executed a GET, but the file has not changed
The resource requested by 305--must be obtained from the address specified by the server
306--the code used in the previous version of HTTP, which is no longer used in the current version
307--declare the requested resource to be temporarily deleted

400--error requests, such as syntax errors
401--Request Authorization failed
402--retains a valid Chargeto header response
403--Request not allowed
404--found no files, queries, or URLs
405--the method defined by the user in the Request-line field does not allow
406--requests for resources to be inaccessible based on accept drag sent by the user
407--is similar to 401, the user must first be authorized on the proxy server
The 408--client did not complete the request within the time specified by the user
409--the current resource state, the request cannot be completed
This resource is no longer available on the 410--server and there is no further reference address
411--server rejects user-defined Content-length property request
412--one or more request header fields errors in the current request
413--requested resource is greater than the size allowed by the server
414--The requested resource URL is longer than the length allowed by the server
Request item format not supported by 415--request Resource
The 416--request contains a range request header field that does not have a range indicating value within the current request resource range, requesting
Also does not contain the If-range request header field
417--server does not meet the expected value specified by the request Expect header field, if it is a proxy server, it may be
First-level servers cannot satisfy the request

500--Server generates internal error
The requested function is not supported by the 501--server
502--servers are temporarily unavailable, sometimes to prevent system overload
503--server overload or suspend repair
504--Gateway overload, the server to use another gateway or service to respond to users, waiting time to set a longer value
505--server does not support or reject the HTTP version specified in the Support request header

==========================================================

English version:

100:continue
101:switching protocols
102:processing

200:ok
201:created
202:accepted
203:non-authoriative Information
204:no Content
205:reset Content
206:partial Content
207:multi-status

300:multiple Choices
301:moved Permanently
302:found
303:see Other
304:not Modified
305:use Proxy
306: (Unused)
307:temporary Redirect

400:bad Request
401:unauthorized
402:payment granted
403:forbidden
404:file 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 satisfiable
417:expectation Failed
422:unprocessable Entity
423:locked
424:failed Dependency

500:internal Server Error
501:not implemented
502:bad Gateway
503:service unavailable
504:gateway Timeout
505:http Version not supported
507:insufficient Storage

Contact Us

The content source of this page is from Internet, which doesn't represent Alibaba Cloud's opinion; products and services mentioned on that page don't have any relationship with Alibaba Cloud. If the content of the page makes you feel confusing, please write us an email, we will handle the problem within 5 days after receiving your email.

If you find any instances of plagiarism from the community, please send an email to: info-contact@alibabacloud.com and provide relevant evidence. A staff member will contact you within 5 working days.

A Free Trial That Lets You Build Big!

Start building with 50+ products and up to 12 months usage for Elastic Compute Service

  • Sales Support

    1 on 1 presale consultation

  • After-Sales Support

    24/7 Technical Support 6 Free Tickets per Quarter Faster Response

  • Alibaba Cloud offers highly flexible support services tailored to meet your exact needs.