/ Web development

HTTP status codes

The following is a list of HTTP response status codes with there standard associated phrases and short description. These status codes are specified by RFC 2616, along with additional, unstandardized status codes sometimes used on Web.
The first digit of the status code specifies one of five classes of response.

Informational (Request received, continuing process.)

Code #	Standard associated phrases	Description
100	Continue	The request was successful. The process can now continue.
101	Info Switching Protocols	The request for the server to switch protocols was accepted, such as a switch from ftp to http.

Success (The action was successfully received, understood, and accepted.)

Code #	Standard associated phrases	Description
200	OK	The item requested of the server is available (keep in mind, available, not accepted or completed).
201	Created	A new address has been created through the use of form posting, perl, cgi, etc..
202	Accepted	The request has been accepted (keep in mind that the request has been accepted, not completed).
203	Non-Authoritative Information	The information received is not from the server that the information was requested from, but from another source.
204	No Content	There was no content to be given for the request. For instance if you click on a hyperlink, imagemap, or button that isn't linked to anything or doesn't do anything.
205	Reset Content	A script has reset the displayed content.
206	Partial Content	Only partial content has been displayed. This could be due to bandwidth, poor caching, bad html, or other reasons.

Redirection (The client must take additional action to complete the request.)

Code #	Standard associated phrases	Description
300	Multiple Choices	You will either get a choice of pages or an error message when this occurs. The address is actually pointing to two multiple files and/or locations.
301	Moved Permanently	The requested page has been permanently moved. The server will automatically redirect you to the new location.
302	Found	The requested page has been temporarily moved. The server will automatically redirect you to the new location.
303	See Other	The requested data is stored in an alternate location and the GET method will be used to retrieve the data. If the actual error is returned then this may be due to a web server misconfiguration.
304	Not Modified	The requested data has not been modified since the last request.
305	Use Proxy	The requested data may only be accessed via the use of a proxy server.
307	Temporary Redirect	The item requested of the server is available (keep in mind, available, not accepted or completed).

Client Error (The request contains bad syntax or cannot be fulfilled.)

Code #	Standard associated phrases	Description
400	Bad Request	The request was denied due to a syntax error in the request.
401	Unauthorized	Your IP address or the username/password you entered were not correct. Your request was denied as you have no permission to access the data.
402	Payment Required	The data is not accessible at the time. The owner of the space has not yet payed their service provider.
403	Forbidden	Your IP address or the username/password you entered were not correct. Your request was denied as you have no permission to access the data. OR The server was unable to serve the data that was requested.
404	Not Found	The document that has been requested either no longer exists, or has never existed on the server.
405	Method Not Allowed	The method you are using to access the document is not allowed. Possible methods include: CONNECT, DELETE, GET, HEAD, OPTIONS, POST, PUT, TRACE
406	Not Acceptable	The client (webbrowser) does not accept the document format. The formats that may be specified not to accept are charset, encoding, certain file types, languages, or ranges.
407	Proxy Authentication Required	The browser has not been authenticated on the required proxy server to access the data. This error is probably most commonly returned by content filters/parental controls.
408	Request Timeout	The server has closed the socket due to communications between the client and server taking too long. This could be due to server load, bandwidth issues, the client being disconnected from the internet, etc.
409	Conflict	Too many requests for the same file at one time. OR There is a conflict with an established software rule. (ie: you are trying to copy over a file with an older version, or you do not have permissions to delete a file) OR This could be caused by a DNS issue.
410	Gone	This is like a 404 error in that the document requested is not on the server, however this differs in that the server 'knows' that the file used to be there and 'believes' that the file may be back, so it returns 410 rather 404.
411	Length Required	When trying to send a document to the server the server did not recieve a Content-Length specification in the header.
412	Precondition Failed	A precondition setting required by the client or server has not been met.
413	Request Entity Too Large	The process is too large to process. (ie: a file you are trying to upload is too large to fit on the server, or a webpage you are trying to download is too large for the server to process)
414	Request-URI Too Large	The URL requested is simply too long. It is most likely more than 1024, 2048, or 4096 characters in length.
415	Unsupported Media Type	This usually occurs if the server does not support the type of media the client is requesting. (ie: the server does not support streaming media, but streaming media is on the server and the client is attempting to access it)
416	Requested Range Not Satisfiable	The client request included a range for acceptable file size, however the document requested did not fit into that range.
417	Expectation Failed	The client's expect header requested certain server behaviors that the server could not perform.

Server Error (The server failed to fulfill an apparently valid request.)

Code #	Standard associated phrases	Description
500	Internal Server Error	The server encountered an error. This is most often caused by a scripting problem, a failed database access attempt, or other similar reasons.
501	Not Implemented	The method you are using to access the document can not be performed by the server. Possible methods include: CONNECT, DELETE, GET, HEAD, OPTIONS, POST, PUT, TRACE.
502	Bad Gateway	The document requested resides on a 3rd party server and the original server received an error from the 3rd party server.
503	Service Unavailable	The server is overloaded or down for maintenance and due to this was unable to process the client request.
504	Gateway Timeout	Most likely the client has lost connectivity (disconnected from the internet) or the cleint's host is having technical difficulties. This could also mean that a server that allows access to the requested server is down, having bandwidth/load issues, or otherwise unavailable.
505	HTTP Version not supported	The server does not support the HTTP version used by the client. (This usually occurs if the server is using an OLDER version of HTTP than the client.)

visit: www.w3.org/Protocols/rfc2616/rfc2616-sec10.html
category: Web development, posted date: 12.07.2006, Comment