HTTP Status Codes

Status Code	Explanation
100	Continue. The server has received the request headers and the client should continue sending the request body.
101	Switching Protocols. The server is switching protocols as requested by the client (for example, upgrading to WebSocket).
102	Processing (WebDAV). The server has accepted the request but has not completed it yet, so the client should not time out.
200	OK. The request succeeded.
201	Created. The request succeeded and a new resource was created as a result.
202	Accepted. The request has been accepted for processing, but processing has not been completed.
203	Non-Authoritative Information. The returned metadata is not exactly the same as is available from the origin server.
204	No Content. The request succeeded but there is no content to send in the response body.
205	Reset Content. The request succeeded and the client should reset the document view.
206	Partial Content. The server is delivering only part of the resource due to a Range header sent by the client.
207	Multi-Status (WebDAV). The response contains multiple status codes for multiple operations.
300	Multiple Choices. The request has more than one possible response and the user agent or user should choose one.
301	Moved Permanently. The resource has been assigned a new permanent URL.
302	Found. Temporary redirect. Clients should keep using the original URL in future requests.
303	See Other. The response to the request can be found under another URI using a GET request.
304	Not Modified. The resource has not changed since the last request (usually used with caching).
305	Use Proxy (deprecated). The requested resource must be accessed through a proxy given by the Location field.
306	Unused (reserved). This code is no longer used.
307	Temporary Redirect. The request should be repeated with another URI, but future requests should still use the original URI.
400	Bad Request. The server cannot or will not process the request due to a client error.
401	Unauthorized. Authentication is required and has failed or has not been provided.
402	Payment Required. Reserved for future use.
403	Forbidden. The client is authenticated but does not have permission to access the resource.
404	Not Found. The requested resource could not be found on the server.
405	Method Not Allowed. The request method is known by the server but not supported by the resource.
406	Not Acceptable. The server cannot generate a response that matches the list of acceptable values defined in the request headers.
407	Proxy Authentication Required. Authentication is required with the proxy.
408	Request Timeout. The server timed out waiting for the request.
409	Conflict. The request conflicts with the current state of the server.
410	Gone. The resource is no longer available and will not be available again.
411	Length Required. The server refuses to accept the request without a defined Content-Length.
412	Precondition Failed. One or more conditions in the request headers evaluated to false on the server.
413	Payload Too Large. The request body is larger than the server is willing or able to process.
414	URI Too Long. The URI requested by the client is longer than the server is willing to interpret.
415	Unsupported Media Type. The request entity has a media type the server does not support.
416	Range Not Satisfiable. The client asked for a portion of the resource that the server cannot supply.
417	Expectation Failed. The server cannot meet the requirements of the Expect request-header field.
421	Misdirected Request. The request was directed at a server that is not able to produce a response (often due to connection reuse).
422	Unprocessable Content (WebDAV). The server understands the content type and syntax but was unable to process the contained instructions.
423	Locked (WebDAV). The resource being accessed is locked.
424	Failed Dependency (WebDAV). The request failed due to failure of a previous request.
425	Too Early. The server is unwilling to risk processing a request that might be replayed.
426	Upgrade Required. The client should switch to a different protocol, given in the Upgrade header.
449	Retry With (non-standard). A Microsoft extension indicating the request should be retried after performing the appropriate action.
500	Internal Server Error. A generic error message when an unexpected condition was encountered.
501	Not Implemented. The server does not support the functionality required to fulfill the request.
502	Bad Gateway. The server received an invalid response from an upstream server.
503	Service Unavailable. The server is not ready to handle the request, often due to maintenance or overload.
504	Gateway Timeout. The server did not receive a timely response from an upstream server.
505	HTTP Version Not Supported. The server does not support the HTTP protocol version used in the request.
506	Variant Also Negotiates. Transparent content negotiation resulted in a circular reference.
507	Insufficient Storage (WebDAV). The server is unable to store the representation needed to complete the request.
508	Loop Detected (WebDAV). The server detected an infinite loop while processing the request.
509	Bandwidth Limit Exceeded (non-standard). The server has exceeded the bandwidth specified by the server administrator.
510	Not Extended. Further extensions to the request are required for the server to fulfill it.