The server refuses to accept the request without a defined Content-Length.
Read the rest of this entry »

The requested resource is no longer available at the server and no forwarding address is known. This condition is expected to be considered permanent. Clients with link editing capabilities SHOULD delete references to the Request-URI after user approval. If the server does not know, or has no facility to determine, whether or not the condition is permanent, the status code 404 (Not Found) SHOULD be used instead. This response is cacheable unless indicated otherwise.
Read the rest of this entry »

The request could not be completed due to a conflict with the current state of the resource. This code is only allowed in situations where it is expected that the user might be able to resolve the conflict and resubmit the request.
Read the rest of this entry »

The client did not produce a request within the time that the server was prepared to wait.
Read the rest of this entry »

This code is similar to 401 (Unauthorized), but indicates that the client must first authenticate itself with the proxy.
Read the rest of this entry »

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.
Read the rest of this entry »

The method specified in the Request-Line is not allowed for the resource identified by the Request-URI.
Read the rest of this entry »

The server has not found anything matching the Request-URI. No indication is given of whether the condition is temporary or permanent.
Read the rest of this entry »

The server understood the request, but is refusing to fulfill it. Authorization will not help and the request SHOULD NOT be repeated.
Read the rest of this entry »

This code is reserved for future use.
Read the rest of this entry »