HTTP STATUS AND ERROR CODES

ANSWER:-

STATUS OR ERROR CODES	DESCRIPTION
STATUS CODES
100	Continue:-  This means that the server has received the request headers, and that the client should proceed to send the request body .If the request body is large, sending it to a server when a request has already been rejected based upon inappropriate headers is inefficient.
101	Switching Protocols:- This means the requester has asked the server to switch protocols and the server is acknowledging that it will do so.
102	Processing:- This code indicates that the server has received and is processing the request, but no response is available yet.
200	OK:- Standard response for successful HTTP requests. The actual response will depend on the request method used.
201	Created:- The request has been fulfilled and resulted in a new resource being created.
202	Accepted:- The request has been accepted for processing, but the processing has not been completed.
203	Non-Authoritative Information (since HTTP/1.1):- The server successfully processed the request, but is returning information that may be from another source.
204	No Content:- The server successfully processed the request, but is not returning any content.
205	Reset Content:- The server successfully processed the request, but is not returning any content.
206	Partial Content:- The server is delivering only part of the resource due to a range header sent by the client.
207	Multi-Status:- The message body that follows is an XML message and can contain a number of separate response codes, depending on how many sub-requests were made.
208	Already Reported:- The members of a DAV binding have already been enumerated in a previous reply to this request, and are not being included again.
226	IM Used:- The server has fulfilled a GET request for the resource, and the response is a representation of the result of one or more instance-manipulations applied to the current instance.
300	Multiple Choices:- Indicates multiple options for the resource that the client may follow.
301	Moved Permanently:- This and all future requests should be directed to the given URI.
302	Found:- This is an example of industry practice contradicting the standard.
303	See other:- The response to the request can be found under another URI using a GET method.
304	Not Modified:- Indicates the resource has not been modified since last requested.
305	Use Proxy:- Many HTTP clients (such as Mozilla and Internet Explorer) do not correctly handle responses with this status code, primarily for security reasons.
306	Switch Proxy:- No longer used.
307	Temporary Redirect:- In this case, the request should be repeated with another URI; however, future requests can still use the original URI.
308	Permanent Redirect:-The request, and all future requests should be repeated using another URI
4XX CLIENT ERROR CODES
400	Bad Request:- The request cannot be fulfilled due to bad syntax.
401	Unauthorized:- Similar to 403 Forbidden, but specifically for use when authentication is possible but has failed or not yet been provided.
402	Payment Required:- Reserved for future use.
403	Forbidden:-The request was a legal request, but the server is refusing to respond to it.
404	Not Found:- The requested resource could not be found but may be available again in the future.
405	Method Not Allowed:- A request was made of a resource using a request method not supported by that resource.
406	Not Acceptable:- The requested resource is only capable of generating content not acceptable according to the Accept headers sent in the request.
407	Proxy Authentication Required:- The client must first authenticate itself with the proxy.
408	Request Timeout:- The server timed out waiting for the request.
409	Conflict:- Indicates that the request could not be processed because of conflict in the request.
410	Gone:- Indicates that the resource requested is no longer available and will not be available again.
411	Length Required:- The request did not specify the length of its content, which is required by the requested resource.
412	Precondition Failed:- The server does not meet one of the preconditions that the requester put on the request.
413	Request Entity Too Large:- The request is larger than the server is willing or able to process
414	Request-URI Too Long:- The URI provided was too long for the server to process.
415	Unsupported Media Type:- The request entity has a media type which the server or resource does not support.
416	Requested Range Not Satisfiable:- The client has asked for a portion of the file, but the server cannot supply that portion.
417	Expectation Failed:- The server cannot meet the requirements of the Expect request-header field.
418	I'm a teapot:- This code was defined in 1998 as one of the traditional IETF April Fools' jokes, in RFC 2324, Hyper Text Coffee Pot Control Protocol, and is not expected to be implemented by actual HTTP servers. However, known implementations do exist.
420	Enhance Your Calm (Twitter):- Returned by the Twitter Search and Trends API when the client is being rate limited.
422	Unprocessable Entity:- The request was well-formed but was unable to be followed due to semantic errors.
423	Locked:- The resource that is being accessed is locked.
424	Failed Dependency:- The request failed due to failure of a previous request.
424	Method Failure:-Indicates the method was not executed on a particular resource within its scope because some part of the method's execution failed causing the entire method to be aborted.
425	Unordered Collection:- Defined in drafts of "WebDAV Advanced Collections Protocol" but not present in "Web Distributed Authoring and Versioning (WebDAV) Ordered Collections Protocol"
426	Upgrade Required:- The client should switch to a different protocol such as TLS/1.0.
428	Precondition Required:- The origin server requires the request to be conditional.
429	Too Many Requests:- The user has sent too many requests in a given amount of time.
431	Request Header Fields Too Large:- The server is unwilling to process the request because either an individual header field, or all the header fields collectively, are too large.
444	No Response:- Used in Nginx logs to indicate that the server has returned no information to the client and closed the connection.
449	Retry With:- A Microsoft extension. The request should be retried after performing the appropriate action
450	Blocked by Windows Parental Controls:- A Microsoft extension. This error is given when Windows Parental Controls are turned on and are blocking access to the given webpage.
451	Unavailable For Legal Reasons:- Defined in the internet draft "A New HTTP Status Code for Legally-restricted Resources”,Intended to be used when resource access is denied for legal reasons,
499	Client Closed Request:- Used in Nginx logs to indicate when the connection has been closed by client while the server is still processing its request, making server unable to send a status code back.
5XX SERVER ERROR CODES
500	Internal Server Error:- A generic error message, given when no more specific message is suitable.
501	Not Implemented:- The server either does not recognise the request method, or it lacks the ability to fulfill the request.
502	Bad Gateway:- The server was acting as a gateway or proxy and received an invalid response from the upstream server
503	Service Unavailable:- The server is currently unavailable (because it is overloaded or down for maintenance).
504	Gateway Timeout:- The server was acting as a gateway or proxy and did not receive a timely response from the 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 for the request results in a circular reference.
507	Insufficient Storage:- The server is unable to store the representation needed to complete the request.
508	Loop Detected:- The server detected an infinite loop while processing the request.
509	Bandwidth Limit Exceeded:- This status code, while used by many servers, is not specified in any RFCs.
510	Not Extended:- Further extensions to the request are required for the server to fulfill it.
511	Network Authentication Required:- The client needs to authenticate to gain network access. Intended for use by intercepting proxies used to control access to the network.
598	Network read timeout error:- This status code is not specified in any RFCs, but is used by Microsoft Corp.
599	Network connect timeout error:-This status code is not specified in any RFCs, but is used by Microsoft Corp.

Thank you :)