Remembering HTTP Status Codes is bit Difficult to remember because there are Lots of Codes and they are very difficult to remember.
GirlieMac, aka Tomomi Imura have won the internet with her deftly conceived and Photoshopped series of HTTP status message. After watching these Pictures you will definitely remember some of the HTTP Codes because I learnt these codes from here Only.
You can get the
Full List from Flickr .
Here are those Codes and basic means of Each Codes-
100 Continue- This means that the server has received the request headers, and that the client should proceed to send the request body.
101 Switching Protocol
101 Switching Protocol- This means the requester has asked the server to switch protocols and the server is acknowledging that it will do so.
200 OK – Standard Response for Successful HTTP request. The actual response will depend on the request method used. 201 Created
201 Created – The request has been fulfilled and resulted in a new resource being created. 202 Accepted
202 Accepted – The request has not been completed but has been accepted for processing and might be disallowed. 204 No Content
204 No Content – The server is not returning any content after successfully processing the request. 207 Multi-Status
207 Multi-Status-Depending on number of sub requests are made, the message body contains many different response codes. 300 Multiple Choice
300 Multiple Choice – It indicates that client can follow multiple options for the resources. 301 Moved Permanently
301 Moved Permanently- In this request it should be directed to the given URI (Uniform Resource Indicator). 302 Found
302 Found- This is an example of industry practice contradicting the standard. Some Web applications and frameworks use the 302 status code 303 See Other
303 See Other – He response to the request can be found under another URI using a GET method. 304 Not Modified
304 Not Modified – Indicates the resource has not been modified since last requested. 305 Use Proxy
305 Use Proxy- Many HTTP clients do not correctly handle responses with this status code, primarily for security reasons. 307 Temporary Redirect
307 Temporary Redirect- In this case, the request should be repeated with another URI but future requests should still use the original URI. 400 Bad Request
400 Bad Request – Due to Bad Syntax, the request could not be filled. 401 Unauthorized
401 Unauthorized- When authentication is required and has failed or has not yet been provided. 402 Payment Required
402 Payment Required Reserved for future use. This code is generally not used, but the original intention was it can be used for some form of Digital Cash. 403 Forbidden
403 Forbidden The request was a valid request, but the server is refusing to respond to it. 404 Not Found
404 Not Found The requested resource could not be found but may be available again in the future. 405 Method Not Allowed
405 Method Not Allowed A request was made of a resource using a request method not supported by that resource. 406 Not Acceptable
406 Not Acceptable The requested resource is only capable of generating content not acceptable according to the Accept headers sent in the request.
408 Request Timeout
408 Request Timeout The server timed out waiting for the request. 409 Conflict
409 Conflict Indicates that the request could not be processed because of conflict in the request. 410 Gone
410 Gone Indicates that the resource requested is no longer available and will not be available again. 411 Length Required
411 Length Required The request did not specify the length of its content, which is required by the requested resource. 413 Request Entity too Large
413 Request Entity too Large The request is larger than the server is willing or able to process. 414 Request-URI Too Long
414 Request-URI Too Long The URI provided was too long for the server to process. 416 Requested Range Not Satisfiable
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
417 Expectation Failed The server cannot meet the requirements of the Expect request-header field. 418 I’m a teapot
418 I’m a teapot This code is not expected to be implemented by actual HTTP servers. 422 Unprocessable Entity
422 Unprocessable Entity The request was well-formed but was unable to be followed due to semantic errors. 423 Locked
423 Locked The resource that is being accessed is locked. 424 Failed Dependency
424 Failed Dependency The request failed due to failure of a previous request. 425 Unordered Collection
425 Unordered Collection Defined in drafts of “WebDAV Advanced Collections Protocol”. 426 Upgrade Required
426 Upgrade Required The client should switch to a different protocol. 429 Too Many Requests
429 Too Many Requests The user has sent too many requests in a given amount of time. 431 Request Header Fields Too Large
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
444 No Response Used in Nginx logs to indicate that the server has returned no information to the client and closed the connection. 450 Blocked by Windows Parental Controls
450 Blocked by Windows Parental Controls A Microsoft extension. 500 Internal Server Error
500 Internal Server Error A generic error message, given when no more specific message is suitable. 502 Bad Gateway
502 Bad Gateway The server was acting as a gateway or proxy and received an invalid response from the upstream server. 503 Service Unavailable
503 Service Unavailable The server is currently unavailable. 506 Variant Also Negotiates
506 Variant Also Negotiates Transparent content negotiation for the request results in a circular reference. 507 Insufficient Storage
507 Insufficient Storage The server is unable to store the representation needed to complete the request. 508 Loop Detected
508 Loop Detected The server detected an infinite loop while processing the request. 509 Bandwidth Limit Exceeded
509 Bandwidth Limit Exceeded This status code, while used by many servers, is not specified in any RFCs. 599 Network connect timeout error
599 Network connect timeout error This status code is not specified in any RFCs, but is used by Microsoft Corp.
Thanks.. Hope you Enjoy.. 🙂