HTTP Error Codes

Switching Protocols
Code	Description	Comment
100	Continue	Â
101	Switching Protocols	Â
Request was successfully received, understood, and accepted
Code	Description	Comment
200	OK	Action complete successfully
201	Created	Success following a POST command
202	Accepted	The request has been accepted for processing, but the processing has not been completed.
203	Partial Information	Response to a GET command, indicates that the returned meta information is from a private overlaid web.
204	No Content	Server has received the request but there is no information to send back.
205	Reset Content	The server has fulfilled the request and the user agent SHOULD reset the document view which caused the request to be sent. This response is primarily intended to allow input for actions to take place via user input, followed by a clearing of the form in which the input is given so that the user can easily initiate another input action. The response MUST NOT include an entity.
206	Partial Content	The requested file was partially sent. Usually caused by stopping or refreshing a web page.
Redirection
Code	Description	Comment
300	Multiple Choices	The requested resource corresponds to any one of a set of representations, each with its own specific location, and agent-driven negotiation information is being provided so that the user (or user agent) can select a preferred representation and redirect its request to that location.
301	Moved Permanently	Requested a directory instead of a file. The web server substituted the index.htm file.
302	Found	The requested resource resides temporarily under a different URI. Since the redirection might be altered on occasion, the client SHOULD continue to use the Request-URI for future requests. This response is only cacheable if indicated by a Cache-Control or Expires header field.
303	See Other	The response to the request can be found under a different URI and SHOULD be retrieved using a GET method on that resource. This method exists primarily to allow the output of a POST-activated script to redirect the user agent to a selected resource. The new URI is not a substitute reference for the originally requested resource. The 303 response MUST NOT be cached, but the response to the second (redirected) request might be cacheable.
304	Not Modified	The cached version of the requested file is the same as the file to be sent.
305	Use Proxy	The requested resource MUST be accessed through the proxy given by the Location field. The Location field gives the URI of the proxy. The recipient is expected to repeat this single request via the proxy. 305 responses MUST only be generated by origin servers.
306	Unused	Reserved for future use
307	Temporary redirect	The requested resource resides temporarily under a different URI.
Client Error
Code	Description	Comment
400	Bad Request	The request could not be understood by the server due to malformed syntax. The client SHOULD NOT repeat the request without modifications.
401	Unauthorized	User fail to provide a valid user name / password required for access to file / directory.
402	Payment Required	Reserved for future use
403	Forbidden	The server understood the request, but is refusing to fulfill it. Authorization will not help and the request SHOULD NOT be repeated.
404	Not Found	The server has not found anything matching the Request-URI. No indication is given of whether the condition is temporary or permanent.
405	Method Not Allowed	The method specified in the Request-Line is not allowed for the resource identified by the Request-URI. The response MUST include an Allow header containing a list of valid methods for the requested resource.
406	Not Acceptable	The resource identified by the request is only capable of generating response entities which have content characteristics not acceptable according to the accept headers sent in the request.
407	Proxy Authentication Required	This code is similar to 401 (Unauthorized), but indicates that the client must first authenticate itself with the proxy.
408	Request Time-Out	The client did not produce a request within the time that the server was prepared to wait. The client MAY repeat the request without modifications at any later time.
409	Conflict	The request could not be completed due to a conflict with the current state of the resource.
410	Gone	The requested resource is no longer available at the server and no forwarding address is known.
411	Length Required	The server refuses to accept the request without a defined Content-Length. The client MAY repeat the request if it adds a valid Content-Length header field containing the length of the message-body in the request message.
412	Precondition Failed	The precondition given in one or more of the request-header fields evaluated to false when it was tested on the server. This response code allows the client to place preconditions on the current resource metainformation (header field data) and thus prevent the requested method from being applied to a resource other than the one intended.
413	Request Entity Too Large	The server is refusing to process a request because the request entity is larger than the server is willing or able to process. The server MAY close the connection to prevent the client from continuing the request.
414	Request-URI Too Large	The server is refusing to service the request because the Request-URI is longer than the server is willing to interpret.
415	Unsupported Media Type	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.
416	Requested Range Not Satisfiable	A server SHOULD return a response with this status code if a request included a Range request-header field
417	Expectation Failed	The expectation given in an Expect request-header field 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
Server Error
Code	Description	Comment
500	Server Error	The server encountered an unexpected condition which prevented it from fulfilling the request
501	Not Implemented	The server does not support the facility required.
502	Bad Gateway	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.
503	Out of Resources	The server cannot process the request due to a system overload. This (should) be a temporary condition.
504	Gateway Time-Out	The service did not respond within the time frame that the gateway was willing to wait.
505	HTTP Version not supported	The server does not support, or refuses to support, the HTTP protocol version that was used in the request message.