{"id":46542,"date":"2024-06-15T03:40:00","date_gmt":"2024-06-15T03:40:00","guid":{"rendered":"https:\/\/www.devopsschool.com\/blog\/?p=46542"},"modified":"2024-06-15T03:40:00","modified_gmt":"2024-06-15T03:40:00","slug":"http-status-code","status":"publish","type":"post","link":"https:\/\/www.devopsschool.com\/blog\/http-status-code\/","title":{"rendered":"HTTP Status Code"},"content":{"rendered":"\n
\"\"<\/figure>\n\n\n\n

Here is a table of common HTTP status codes with their explanations:<\/p>\n\n\n\n

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

Here is a table of common HTTP status codes with their explanations: Status Code Description 100 Continue – The server has received the request headers, and the client should proceed to send the request body. 101 Switching Protocols – The requester has asked the server to switch protocols, and the server is acknowledging that it…<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"","sticky":false,"template":"","format":"standard","meta":{"_kad_post_transparent":"","_kad_post_title":"","_kad_post_layout":"","_kad_post_sidebar_id":"","_kad_post_content_style":"","_kad_post_vertical_padding":"","_kad_post_feature":"","_kad_post_feature_position":"","_kad_post_header":false,"_kad_post_footer":false,"_kad_post_classname":"","_joinchat":[],"footnotes":""},"categories":[2],"tags":[],"class_list":["post-46542","post","type-post","status-publish","format-standard","hentry","category-uncategorised"],"_links":{"self":[{"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/posts\/46542","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/comments?post=46542"}],"version-history":[{"count":1,"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/posts\/46542\/revisions"}],"predecessor-version":[{"id":46544,"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/posts\/46542\/revisions\/46544"}],"wp:attachment":[{"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/media?parent=46542"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/categories?post=46542"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/tags?post=46542"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}