Hypertext Transfer Protocol (HTTP) is a communications protocol for the transfer of information on intranets and the World Wide Web. Its original purpose was to provide a way to publish and retrieve hypertext pages over the Internet. HTTP is a request/response standard between a client and a server. A client is the end-user, the server is the web site. In this short article you can find Numeric Order List of HTTP/1.1 Reply Codes as a reference. All codes in the table are linked to other articles which describe specific response code deeper.
Read the rest of this entry »

The server does not support, or refuses to support, the HTTP protocol version that was used in the request message.
Read the rest of this entry »

The server, while acting as a gateway or proxy, did not receive a timely response from the upstream server specified by the URI (e.g. HTTP, FTP, LDAP) or some other auxiliary server (e.g. DNS) it needed to access in attempting to complete the request.
Read the rest of this entry »

The server is currently unable to handle the request due to a temporary overloading or maintenance of the server. The implication is that this is a temporary condition which will be alleviated after some delay.
Read the rest of this entry »

The server, while acting as a gateway or proxy, received an invalid response from the upstream server it accessed in attempting to fulfill the request.
Read the rest of this entry »

The server does not support the functionality required to fulfill the request. This is the appropriate response when the server does not recognize the request method and is not capable of supporting it for any resource.
Read the rest of this entry »

The server encountered an unexpected condition which prevented it from fulfilling the request.
Read the rest of this entry »

The expectation given in an Expect request-header field (see section 14.20 of the RFC 2616) could not be met by this server, or, if the server is a proxy, the server has unambiguous evidence that the request could not be met by the next-hop server.
Read the rest of this entry »

A server SHOULD return a response with this status code if a request included a Range request-header field (section 14.35 of the RFC 2616), and none of the range-specifier values in this field overlap the current extent of the selected resource, and the request did not include an If-Range request-header field. (For byte-ranges, this means that the first-byte-pos of all of the byte-range-spec values were greater than the current length of the selected resource.)
Read the rest of this entry »

The server is refusing to service the request because the entity of the request is in a format not supported by the requested resource for the requested method.
Read the rest of this entry »