Limited Time Offer!

For Less Than the Cost of a Starbucks Coffee, Access All DevOpsSchool Videos on YouTube Unlimitedly.
Master DevOps, SRE, DevSecOps Skills!

Enroll Now
Uncategorised

HTTP Status Code

June 15, 2024 Leave a Comment

Here is a table of common HTTP status codes with their explanations:

Status CodeDescription
100Continue – The server has received the request headers, and the client should proceed to send the request body.
101Switching Protocols – The requester has asked the server to switch protocols, and the server is acknowledging that it will do so.
200OK – The request has succeeded. The information returned with the response is dependent on the method used in the request.
201Created – The request has been fulfilled and has resulted in one or more new resources being created.
202Accepted – The request has been accepted for processing, but the processing has not been completed.
203Non-Authoritative Information – The server is a transforming proxy (e.g. a web accelerator) that received a 200 OK from its origin, but is returning a modified response.
204No Content – The server successfully processed the request and is not returning any content.
205Reset Content – The server successfully processed the request, but is not returning any content, and requires that the requester reset the document view.
206Partial Content – The server is delivering only part of the resource due to a range header sent by the client.
300Multiple Choices – There are multiple options for the resource that the client may follow.
301Moved Permanently – This and all future requests should be directed to the given URI.
302Found – The requested resource resides temporarily under a different URI.
303See Other – The response to the request can be found under another URI using a GET method.
304Not Modified – The resource has not been modified since the version specified by the request headers.
305Use Proxy – The requested resource is available only through a proxy, whose address is provided in the response.
307Temporary Redirect – In this case, the request should be repeated with another URI; however, future requests should still use the original URI.
400Bad Request – The server cannot or will not process the request due to an apparent client error.
401Unauthorized – Similar to 403 Forbidden, but specifically for use when authentication is required and has failed or has not yet been provided.
402Payment Required – Reserved for future use.
403Forbidden – The request was valid, but the server is refusing action.
404Not Found – The requested resource could not be found but may be available in the future.
405Method Not Allowed – A request method is not supported for the requested resource.
406Not Acceptable – The requested resource is capable of generating only content not acceptable according to the Accept headers sent in the request.
407Proxy Authentication Required – The client must first authenticate itself with the proxy.
408Request Timeout – The server timed out waiting for the request.
409Conflict – The request could not be processed because of conflict in the request, such as an edit conflict between multiple simultaneous updates.
410Gone – The resource requested is no longer available and will not be available again.
411Length Required – The request did not specify the length of its content, which is required by the requested resource.
412Precondition Failed – The server does not meet one of the preconditions that the requester put on the request.
413Payload Too Large – The request is larger than the server is willing or able to process.
414URI Too Long – The URI provided was too long for the server to process.
415Unsupported Media Type – The request entity has a media type which the server or resource does not support.
416Range Not Satisfiable – The client has asked for a portion of the file (byte serving), but the server cannot supply that portion.
417Expectation Failed – The server cannot meet the requirements of the Expect request-header field.
418I’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.
421Misdirected Request – The request was directed at a server that is not able to produce a response.
422Unprocessable Entity – The request was well-formed but was unable to be followed due to semantic errors.
423Locked – The resource that is being accessed is locked.
424Failed Dependency – The request failed due to failure of a previous request.
425Too Early – Indicates that the server is unwilling to risk processing a request that might be replayed.
426Upgrade Required – The client should switch to a different protocol such as TLS/1.0.
428Precondition Required – The origin server requires the request to be conditional.
429Too Many Requests – The user has sent too many requests in a given amount of time.
431Request Header Fields Too Large – The server is unwilling to process the request because its header fields are too large.
451Unavailable For Legal Reasons – The user requests an illegal resource, such as a web page censored by a government.
500Internal Server Error – A generic error message, given when an unexpected condition was encountered and no more specific message is suitable.
501Not Implemented – The server either does not recognize the request method, or it lacks the ability to fulfill the request.
502Bad Gateway – The server was acting as a gateway or proxy and received an invalid response from the upstream server.
503Service Unavailable – The server cannot handle the request (because it is overloaded or down for maintenance).
504Gateway Timeout – The server was acting as a gateway or proxy and did not receive a timely response from the upstream server.
505HTTP Version Not Supported – The server does not support the HTTP protocol version used in the request.
506Variant Also Negotiates – Transparent content negotiation for the request results in a circular reference.
507Insufficient Storage – The server is unable to store the representation needed to complete the request.
508Loop Detected – The server detected an infinite loop while processing a request.
510Not Extended – Further extensions to the request are required for the server to fulfill it.
511Network Authentication Required – The client needs to authenticate to gain network access.
Rajesh Kumar
Follow me
Latest posts by Rajesh Kumar (see all)
Subscribe
Notify of
guest
0 Comments
Newest
Oldest Most Voted
Inline Feedbacks
View all comments
0
Would love your thoughts, please comment.x
()
x