Edit filter log

'<!-- This article is British English, in particular "fulfil" is a valid spelling. See [[WP:ENGVAR]] --> {{HTTP}} This is a list of '''[[Hypertext Transfer Protocol]] (HTTP) response status codes'''. It includes codes from IETF [[Request for Comments]] (RFCs), other specifications, and some additional codes used in some common applications of the [[Hypertext Transfer Protocol]] (HTTP). The first digit of the status code specifies one of five standard classes of responses. The message phrases shown are typical, but any human-readable alternative may be provided. Unless otherwise stated, the status code is part of the HTTP/1.1 standard (RFC 7231).<ref>{{cite web|title=Hypertext Transfer Protocol -- HTTP/1.1|url=https://tools.ietf.org/html/rfc2616|website=IETF|accessdate=16 October 2015}}</ref> The [[Internet Assigned Numbers Authority]] (IANA) maintains the official registry of HTTP status codes.<ref name="iana_status_codes">{{cite web|url=http://www.iana.org/assignments/http-status-codes/|title=Hypertext Transfer Protocol (HTTP) Status Code Registry|publisher=Iana.org|accessdate=January 8, 2015}}</ref> Microsoft [[Internet Information Services]] (IIS) sometimes uses additional decimal sub-codes for more specific information,<ref name="MS_KB943891">{{cite web | url = http://support.microsoft.com/kb/943891/ | title = The HTTP status codes in IIS 7.0 | date = July 14, 2009 | publisher = [[Microsoft]] | accessdate = April 1, 2009 }}</ref> however these sub-codes only appear in the response payload and in documentation, not in the place of an actual HTTP status code. ==1xx Informational responses== An informational response indicates that the request was received and understood. It is issued on a provisional basis while request processing continues. It alerts the client to wait for a final response. The message consists only of the status line and optional header fields, and is terminated by an empty line. As the HTTP/1.0 standard did not define any 1xx status codes, servers ''must not''<ref group="note">Italicised words and phrases such as ''must'' and ''should'' represent interpretation guidelines as given by RFC 2119</ref> send a 1xx response to an HTTP/1.0 compliant client except under experimental conditions.<ref>{{cite web|title=10 Status Code Definitions|url=http://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html|website=W3|accessdate=16 October 2015}}</ref> ;{{anchor |100}}100 Continue : The server has received the request headers and the client should proceed to send the request body (in the case of a request for which a body needs to be sent; for example, a [[POST (HTTP)|POST]] request). Sending a large request body to a server after a request has been rejected for inappropriate headers would be inefficient. To have a server check the request's headers, a client must send <code>Expect: 100-continue</code> as a header in its initial request and receive a <code>100 Continue</code> status code in response before sending the body. The response <code>417 Expectation Failed</code> indicates the request should not be continued.<ref name="iana_status_codes" /> ;{{anchor |101}}101 Switching Protocols : The requester has asked the server to switch protocols and the server has agreed to do so.<ref>{{cite web|title=101|url=http://httpstatus.es/101|website=httpstatus|accessdate=16 October 2015}}</ref> ;{{anchor |102}}102 Processing ([[WebDAV]]; RFC 2518) : A WebDAV request may contain many sub-requests involving file operations, requiring a long time to complete the request. This code indicates that the server has received and is processing the request, but no response is available yet.<ref name="RFC_2518">{{cite IETF | title = HTTP Extensions for Distributed Authoring – WEBDAV | rfc = 2518 | last1 = Goland | first1 = Yaronn | authorlink1 = | last2 = Whitehead | first2 = Jim | authorlink2 = Jim Whitehead (professor) | last3 = Faizi | first3 = Asad | authorlink3 = | last4 = Carter | first4 = Steve R. | authorlink4 = | last5 = Jensen | first5 = Del | authorlink5 = | year = 1999 | month = February | publisher = [[Internet Engineering Task Force|IETF]] | accessdate = October 24, 2009 }}</ref> This prevents the client from timing out and assuming the request was lost. ==2xx Success== This class of status codes indicates the action requested by the client was received, understood, accepted, and processed successfully.<ref name="iana_status_codes" /> ;{{anchor |200}}200 OK : Standard response for successful HTTP requests. The actual response will depend on the request method used. In a GET request, the response will contain an entity corresponding to the requested resource. In a POST request, the response will contain an entity describing or containing the result of the action.<ref name="RFC_2616">{{cite_IETF | title = Hypertext Transfer Protocol -- HTTP/1.1 | rfc = 2616 | year = 1999| month = June | sectionname = 200 OK | section= 10.2.1 | publisher = [[Internet Engineering Task Force|IETF]] | accessdate = August 30, 2016 }}</ref> ;{{anchor |201}}201 Created : The request has been fulfilled, resulting in the creation of a new resource.<ref>{{cite web|last1=Stewart|first1=Mark|last2=djna|title=Create request with POST, which response codes 200 or 201 and content|url=https://stackoverflow.com/questions/1860645/create-request-with-post-which-response-codes-200-or-201-and-content|website=Stack Overflow|accessdate=16 October 2015}}</ref> ;{{anchor |202}}202 Accepted : The request has been accepted for processing, but the processing has not been completed. The request might or might not be eventually acted upon, and may be disallowed when processing occurs.<ref>{{cite web|title=202|url=http://httpstatus.es/202|website=httpstatus|accessdate=16 October 2015}}</ref> ;{{anchor |203}}203 Non-Authoritative Information (since HTTP/1.1) : The server is a transforming proxy (e.g. a [[Web accelerator]]) that received a 200 OK from its origin, but is returning a modified version of the origin's response.<ref>{{cite web|title = RFC 7231, Section 6.3.4.|url = https://tools.ietf.org/html/rfc7231#section-6.3.4|website = |accessdate = }}</ref><ref>{{cite web|title = RFC 7230, Section 5.7.2.|url = https://tools.ietf.org/html/rfc7230#section-5.7.2}}</ref> ;{{anchor |204}}204 No Content : The server successfully processed the request and is not returning any content.<ref>{{cite web|last1=Simmance|first1=Chris|title=Server Response Codes And What They Mean|url=http://www.koozai.com/blog/analytics/server-response-codes-and-what-they-mean/|website=koozai|accessdate=16 October 2015}}</ref> ;{{anchor |205}}205 Reset Content : The server successfully processed the request, but is not returning any content. Unlike a 204 response, this response requires that the requester reset the document view.<ref>{{cite web|last1=ikitommi|last2=Deraen|title=metosin/ring-http-response|url=https://github.com/metosin/ring-http-response/blob/master/dev/user.clj|website=GitHub|accessdate=16 October 2015}}</ref> ;{{anchor |206}}206 Partial Content (RFC 7233) : The server is delivering only part of the resource ([[byte serving]]) due to a range header sent by the client. The range header is used by HTTP clients to enable resuming of interrupted downloads, or split a download into multiple simultaneous streams.<ref>{{cite web|title=diff --git a/linkchecker.module b/linkchecker.module|url=https://www.drupal.org/files/issues/linkchecker-report-descriptions-2403161-1.patch|website=Drupal|accessdate=16 October 2015}}</ref> ;{{anchor |207}}207 Multi-Status (WebDAV; RFC 4918) : 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.<ref name="RFC_4918"/> ;{{anchor |208}}208 Already Reported (WebDAV; RFC 5842) : The members of a DAV binding have already been enumerated in a preceding part of the (multistatus) response, and are not being included again. ;{{anchor |226}}226 IM Used (RFC 3229) : The server has fulfilled a request for the resource, and the response is a representation of the result of one or more instance-manipulations applied to the current instance.<ref name="RFC_3229">{{cite IETF | title = Delta encoding in HTTP | rfc = 3229 | year = 2002 | month = January | publisher = [[Internet Engineering Task Force|IETF]] | accessdate = February 25, 2011 }}</ref> ==3xx Redirection== This class of status code indicates the client must take additional action to complete the request. Many of these status codes are used in [[URL redirection]].<ref name="iana_status_codes" /> A user agent may carry out the additional action with no user interaction only if the method used in the second request is GET or HEAD. A user agent may automatically redirect a request. A user agent should detect and intervene to prevent cyclical redirects.<ref>{{cite web|url=http://tools.ietf.org/html/rfc7231#section-6.4|title=Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content|website=IETF|accessdate=13 February 2016}}</ref> ;{{anchor |300}}300 Multiple Choices : Indicates multiple options for the resource from which the client may choose (via [[content negotiation#Agent-driven|agent-driven content negotiation]]). For example, this code could be used to present multiple video format options, to list files with different [[filename extension]]s, or to suggest [[word-sense disambiguation]].<ref>{{cite web|title=300|url=http://httpstatus.es/300|website=httpstatus|accessdate=16 October 2015}}</ref> ;{{anchor |301}}[[HTTP 301|301 Moved Permanently]] : This and all future requests should be directed to the given [[Uniform resource identifier|URI]].<ref>{{cite web|title=301|url=http://httpstatus.es/301|website=httpstatus|accessdate=16 October 2015}}</ref> ;{{anchor |302}}[[HTTP 302|302 Found]] : This is an example of industry practice contradicting the standard. The HTTP/1.0 specification (<nowiki>RFC 1945</nowiki>) required the client to perform a temporary redirect (the original describing phrase was "Moved Temporarily"),<ref name="RFC_1945">{{cite IETF | title = Hypertext Transfer Protocol – HTTP/1.0 | rfc = 1945 | last1 = Berners-Lee | first1 = Tim | authorlink1 = Tim Berners-Lee | last2 = Fielding | first2 = Roy T. | authorlink2 = Roy Fielding | last3 = Nielsen | first3 = Henrik Frystyk | authorlink3 = Henrik Frystyk Nielsen | year = 1996 | month = May | publisher = [[Internet Engineering Task Force|IETF]] | accessdate = October 24, 2009 }}</ref> but popular browsers implemented 302 with the functionality of a 303 See Other. Therefore, HTTP/1.1 added status codes 303 and 307 to distinguish between the two behaviours.<ref name="RFC7230-10">{{cite web | url = http://tools.ietf.org/html/rfc7231#section-6.4 | title = Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content, Section 6.4 | publisher = [[IETF]] | accessdate = June 12, 2014 }}</ref> However, some Web applications and frameworks use the 302 status code as if it were the 303.<ref name="ruby-on-rails-ActionController-Redirecting-redirect_to">{{cite web | url = http://api.rubyonrails.org/classes/ActionController/Redirecting.html#method-i-redirect_to | title = Reference of method redirect_to in Ruby Web Framework "Ruby on Rails". It states: The redirection happens as a "302 Moved" header unless otherwise specified. | accessdate = June 30, 2012 }}</ref> ;{{anchor |303}}[[HTTP 303|303 See Other]] (since HTTP/1.1) : The response to the request can be found under another [[Uniform Resource Identifier|URI]] using a GET method. When received in response to a POST (or PUT/DELETE), the client should presume that the server has received the data and should issue a redirect with a separate GET message.<ref>{{cite web|title=303|url=http://httpstatus.es/303|website=httpstatus|accessdate=16 October 2015}}</ref> ;{{anchor |304}}304 Not Modified (RFC 7232) : Indicates that the resource has not been modified since the version specified by the [[List of HTTP header fields#Request Headers|request headers]] If-Modified-Since or If-None-Match. In such case, there is no need to retransmit the resource since the client still has a previously-downloaded copy.<ref>{{cite web|last1=Brown|first1=Kevin|last2=CRS...|title=getting 304 response even with django-cors-headers|url=https://stackoverflow.com/questions/27527547/getting-304-response-even-with-django-cors-headers|website=Stack Overflow|accessdate=16 October 2015}}</ref> ;{{anchor |305}}305 Use Proxy (since HTTP/1.1) :The requested resource is available only through a proxy, the address for which is provided in the response. Many HTTP clients (such as [[Mozilla]]<ref name="mozilla bugzilla bug 187996">{{cite web | url = https://bugzilla.mozilla.org/show_bug.cgi?id=187996 | title = Mozilla Bugzilla Bug 187996: Strange behavior on 305 redirect | date = March 3, 2003 | accessdate = May 21, 2009}}</ref> and [[Internet Explorer]]) do not correctly handle responses with this status code, primarily for security reasons.<ref name="mozilla bugzilla bug 187996 comment 13">{{cite web | url = https://bugzilla.mozilla.org/show_bug.cgi?id=187996#c13 | title = Mozilla Bugzilla Bug 187996: Strange behavior on 305 redirect, comment 13 | date = March 3, 2003 | accessdate = May 21, 2009}}</ref> ;{{anchor |306}}306 Switch Proxy : No longer used. Originally meant "Subsequent requests should use the specified proxy."<ref>{{cite web |last=Cohen |first=Josh |title=HTTP/1.1 305 and 306 Response Codes |url=https://tools.ietf.org/html/draft-cohen-http-305-306-responses-00 |publisher=HTTP Working Group }}</ref> ;{{anchor |307}}307 Temporary Redirect (since HTTP/1.1) : In this case, the request should be repeated with another URI; however, future requests should still use the original URI. In contrast to how 302 was historically implemented, the request method is not allowed to be changed when reissuing the original request. For example, a POST request should be repeated using another POST request.<ref name="SemanticsAndContent">{{cite web | url = https://tools.ietf.org/html/rfc7231#section-6.4.7 | title = Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content, Section 6.4.7 307 Temporary Redirect | year = 2014 | publisher=[[IETF]] | accessdate= September 20, 2014 }}</ref> ;{{anchor |308}}308 Permanent Redirect (RFC 7538) : The request and all future requests should be repeated using another URI. 307 and 308 parallel the behaviors of 302 and 301, but ''do not allow the HTTP method to change''. So, for example, submitting a form to a permanently redirected resource may continue smoothly.<ref name="rfc7238">{{cite web | url = https://tools.ietf.org/html/rfc7538 | title = The Hypertext Transfer Protocol Status Code 308 (Permanent Redirect) | date = April 2015 | publisher = Internet Engineering Task Force | accessdate = 2015-04-06 }}</ref> ==4xx Client errors== [[File:404 error sample.png|alt=A 404 error on Wikipedia.|thumb|404 error on [[Wikipedia]]]] The 4xx class of status codes is intended for situations in which the client seems to have erred. Except when responding to a HEAD request, the server ''should'' include an entity containing an explanation of the error situation, and whether it is a temporary or permanent condition. These status codes are applicable to any request method. User agents ''should'' display any included entity to the user.<ref>{{cite web|title=E Explanation of Failure Codes|url=https://docs.oracle.com/cd/E14269_01/doc.451/e14266/result_codes.htm|website=Oracle|accessdate=16 October 2015}}</ref> ;{{anchor |400}}400 Bad Request : The server cannot or will not process the request due to an apparent client error (e.g., malformed request syntax, too large size, invalid request message framing, or deceptive request routing).<ref name="rfc7231-400">{{cite web|url=https://tools.ietf.org/html/rfc7231#section-6.5.1 |title=RFC7231 on code 400|publisher=Tools.ietf.org|accessdate=January 8, 2015}}</ref> ;{{anchor |401}}401 Unauthorized (RFC 7235) : Similar to ''403 Forbidden'', but specifically for use when authentication is required and has failed or has not yet been provided. The response must include a WWW-Authenticate header field containing a challenge applicable to the requested resource. See [[Basic access authentication]] and [[Digest access authentication]].<ref>{{cite web|title=401|url=http://httpstatus.es/401|website=httpstatus|accessdate=16 October 2015}}</ref> 401 semantically means [[Authentication|"unauthenticated"]],<ref name="rfc7235-401">{{cite web|url=https://tools.ietf.org/html/rfc7235#section-3.1 |title=RFC7235 on code 401|publisher=Tools.ietf.org|accessdate=February 8, 2015}}</ref> i.e. the user does not have the necessary credentials. : Note: Some sites issue HTTP 401 when an [[IP address]] is banned from the website (usually the website domain) and that specific address is refused permission to access a website. ;{{anchor |402}}402 Payment Required : Reserved for future use. The original intention was that this code might be used as part of some form of [[digital cash]] or [[micropayment]] scheme, but that has not happened, and this code is not usually used. [[Google Developers]] API uses this status if a particular developer has exceeded the daily limit on requests.<ref name="GoogleDevelopersErrorCode"> {{cite web | url = https://developers.google.com/doubleclick-search/v2/standard-error-responses | title = Google API Standard Error Responses | year = 2015 | publisher=[[Google]] | accessdate=September 24, 2015 }}</ref> ;{{anchor |403}}[[HTTP 403|403 Forbidden]] : The request was valid, but the server is refusing action. The user might not have the necessary permissions for a resource. ;{{anchor |404}}[[HTTP 404|404 Not Found]] : The requested resource could not be found but may be available in the future. Subsequent requests by the client are permissible.<ref>{{cite web|title=Introduction|url=http://support.qas.com/ua/en-us/Capture/PhoneAPI/Content/Introduction/Introduction_API_Sync.htm|website=QAS|accessdate=16 October 2015}}</ref> ;{{anchor |405}}405 Method Not Allowed : A request method is not supported for the requested resource; for example, a GET request on a form that requires data to be presented via [[POST (HTTP)|POST]], or a PUT request on a read-only resource. ;{{anchor |406}}406 Not Acceptable : The requested resource is capable of generating only content not acceptable according to the Accept headers sent in the request.<ref>{{cite web|last1=Singh|first1=Prabhat|last2=user1740567|title=Spring 3.x JSON status 406 "characteristics not acceptable according to the request "accept" headers ()"|url=https://stackoverflow.com/questions/12865093/spring-3-x-json-status-406-characteristics-not-acceptable-according-to-the-requ|website=Stack Overflow|accessdate=16 October 2015}}</ref> See [[Content negotiation]]. ;{{anchor |407}}407 Proxy Authentication Required (RFC 7235) :The client must first authenticate itself with the [[Proxy server|proxy]].<ref>{{cite web|title=407|url=http://httpstatus.es/407|website=httpstatus|accessdate=16 October 2015}}</ref> ;{{anchor |408}}408 Request Timeout : The server timed out waiting for the request. According to HTTP specifications: "The client did not produce a request within the time that the server was prepared to wait. The client MAY repeat the request without modifications at any later time."<ref>{{cite web|title=408|url=http://httpstatus.es/408|website=httpstatus|accessdate=16 October 2015}}</ref> ;{{anchor |409}}409 Conflict : Indicates that the request could not be processed because of conflict in the request, such as an [[edit conflict]] between multiple simultaneous updates. ;{{anchor |410}}410 Gone : Indicates that the resource requested is no longer available and will not be available again. This should be used when a resource has been intentionally removed and the resource should be purged. Upon receiving a 410 status code, the client should not request the resource in the future. Clients such as search engines should remove the resource from their indices.<ref name="HTTP_410"> {{cite web | url = https://www.youtube.com/watch?v=xp5Nf8ANfOw | title = Does Google treat 404 and 410 status codes differently? (Youtube) | year = 2014 | publisher=[[Google]] | accessdate=February 4, 2015 }}</ref> Most use cases do not require clients and search engines to purge the resource, and a "404 Not Found" may be used instead. ;{{anchor |411}}411 Length Required : The request did not specify the length of its content, which is required by the requested resource.<ref>{{cite web|title=List of HTTP status codes|url=https://books.google.co.uk/books?id=J1gb2eb-NuEC&pg=PA197&lpg=PA197&dq=The+request+did+not+specify+the+length+of+its+content,+which+is+required+by+the+requested+resource.&source=bl&ots=o4rBopF2G4&sig=f_IFpmPcMqrSBLxhhf0yVVPedYU&hl=en&sa=X&ved=0CDEQ6AEwA2oVChMIo6KixN3HyAIVRhkeCh3xAw04#v=onepage&q=The%20request%20did%20not%20specify%20the%20length%20of%20its%20content%2C%20which%20is%20required%20by%20the%20requested%20resource.&f=false|website=Google Books|accessdate=16 October 2015}}</ref> ;{{anchor |412}}412 Precondition Failed (RFC 7232) : The server does not meet one of the preconditions that the requester put on the request.<ref>{{cite web|last1=Kowser|last2=Patel|first2=Amit|title=REST response code for invalid data|url=https://stackoverflow.com/questions/6123425/rest-response-code-for-invalid-data|website=Stack Overflow|accessdate=16 October 2015}}</ref> ;{{anchor |413}}413 Payload Too Large (RFC 7231) : The request is larger than the server is willing or able to process. Previously called "Request Entity Too Large".<ref>{{cite web|url=https://tools.ietf.org/html/rfc2616#section-10.4.14 |title=RFC2616 on status 413|publisher=Tools.ietf.org|accessdate=November 11, 2015}}</ref> ;{{anchor |414}}414 URI Too Long (RFC 7231) : The [[URI]] provided was too long for the server to process. Often the result of too much data being encoded as a query-string of a GET request, in which case it should be converted to a POST request.<ref>{{cite web|last1=user27828|title=GET Request - Why is my URI so long?|url=https://stackoverflow.com/questions/20157706/get-request-why-is-my-uri-so-long|website=Stack Overflow|accessdate=16 October 2015}}</ref> Called "Request-URI Too Long" previously.<ref>{{cite web|url=https://tools.ietf.org/html/rfc2616#section-10.4.15 |title=RFC2616 on status 414|publisher=Tools.ietf.org|accessdate=November 11, 2015}}</ref> ;{{anchor |415}}415 Unsupported Media Type : The request entity has a [[Internet media type|media type]] which the server or resource does not support. For example, the client uploads an image as [[Scalable Vector Graphics|image/svg+xml]], but the server requires that images use a different format. ;{{anchor |416}}416 Range Not Satisfiable (RFC 7233) : The client has asked for a portion of the file ([[byte serving]]), but the server cannot supply that portion. For example, if the client asked for a part of the file that lies beyond the end of the file.<ref>{{cite web|last1=Sigler|first1=Chris|title=416 Requested Range Not Satisfiable|url=http://getstatuscode.com/416|website=GetStatusCode|accessdate=16 October 2015}}</ref> Called "Requested Range Not Satisfiable" previously.<ref>{{cite web|url=https://tools.ietf.org/html/rfc2616#section-10.4.17 |title=RFC2616 on status 416|publisher=Tools.ietf.org|accessdate=November 11, 2015}}</ref> ;{{anchor |417}}417 Expectation Failed : The server cannot meet the requirements of the Expect request-header field.<ref>{{cite web|last1=TheDeadLike|title=HTTP/1.1 Status Codes 400 and 417, cannot choose which|url=http://serverfault.com/questions/433470/http-1-1-status-codes-400-and-417-cannot-choose-which|website=serverFault|accessdate=16 October 2015}}</ref> <!-- The following code is under discussion on the talk page. Please discuss there before removing this entry. --> ;{{anchor |418}}418 I'm a teapot (RFC 2324) :This code was defined in 1998 as one of the traditional [[Internet Engineering Task Force|IETF]] [[April Fools' Day RFC|April Fools' jokes]], in RFC 2324, ''[[Hyper Text Coffee Pot Control Protocol]]'', and is not expected to be implemented by actual HTTP servers. The RFC specifies this code should be returned by teapots requested to brew coffee.<ref>{{cite IETF |rfc=2324 |author=Larry Masinter |date=1 April 1998 |title=Hyper Text Coffee Pot Control Protocol (HTCPCP/1.0) }}</ref> This HTTP status is used as an [[Easter egg (media)|Easter egg]] in some websites, including [[Google.com]].<ref>{{cite news |url=http://searchengineland.com/new-google-easter-egg-seo-geeks-server-status-418-im-teapot-201739 |author=Barry Schwartz |date=26 August 2014 |title=New Google Easter Egg For SEO Geeks: Server Status 418, I’m A Teapot |work=Search Engine Land }}</ref> ;{{anchor |421}}421 Misdirected Request (RFC 7540) : The request was directed at a server that is not able to produce a response (for example because a connection reuse).<ref name=HTTP2>{{cite web | url = http://http2.github.io/http2-spec/#MisdirectedRequest | title = Hypertext Transfer Protocol version 2 | authorlink1 = M. Belshe | authorlink2 = R. Peon | authorlink3 = M. Thomson, Editor |date=March 2015 | accessdate = April 25, 2015 }}</ref> ;{{anchor |422}}422 Unprocessable Entity (WebDAV; RFC 4918) : The request was well-formed but was unable to be followed due to semantic errors.<ref name="RFC_4918">{{cite IETF | title = HTTP Extensions for Web Distributed Authoring and Versioning (WebDAV) | rfc = 4918 | editor-last = Dusseault | editor-first = Lisa | editor-link = | year = 2007 | month = June | publisher = [[Internet Engineering Task Force|IETF]] | accessdate = October 24, 2009 }}</ref> ;{{anchor |423}}423 Locked (WebDAV; RFC 4918) : The resource that is being accessed is locked.<ref name="RFC_4918"/> ;{{anchor |424}}424 Failed Dependency (WebDAV; RFC 4918) : The request failed due to failure of a previous request (e.g., a PROPPATCH).<ref name="RFC_4918"/> ;{{anchor |426}}426 Upgrade Required : The client should switch to a different protocol such as [[Transport Layer Security|TLS/1.0]], given in the [[Upgrade header]] field.<ref>{{cite web|last1=Khare|first1=R|last2=Lawrence|first2=S|title=Upgrading to TLS Within HTTP/1.1|url=https://tools.ietf.org/html/rfc2817|website=IETF|publisher=Network Working Group|accessdate=16 October 2015}}</ref> ;{{anchor|428}}428 Precondition Required (RFC 6585) :The origin server requires the request to be conditional. Intended to prevent "the 'lost update' problem, where a client GETs a resource's state, modifies it, and PUTs it back to the server, when meanwhile a third party has modified the state on the server, leading to a conflict."<ref name="rfc6585">{{cite web |url=http://tools.ietf.org/html/rfc6585 |title=RFC 6585 – Additional HTTP Status Codes |first1=M. |last1=Nottingham |first2=R. |last2=Fielding |date=April 2012 |work=Request for Comments |publisher=[[Internet Engineering Task Force]] |accessdate=May 1, 2012}}</ref> ;{{anchor|429}}429 Too Many Requests (RFC 6585) :The user has sent too many requests in a given amount of time. Intended for use with [[rate limiting|rate-limiting]] schemes.<ref name="rfc6585"/> ;{{anchor|431}}431 Request Header Fields Too Large (RFC 6585) :The server is unwilling to process the request because either an individual header field, or all the header fields collectively, are too large.<ref name="rfc6585"/> ;{{anchor|451}}[[HTTP 451|451 Unavailable For Legal Reasons]] ([[rfc:7725|RFC 7725]]) : A server operator has received a legal demand to deny access to a resource or to a set of resources that includes the requested resource.<ref>{{cite web|title=An HTTP Status Code to Report Legal Obstacles|url=https://tools.ietf.org/html/rfc7725|date=February 2016|last=Bray|first=T.|accessdate=7 March 2015|website=ietf.org}}</ref> The code 451 was chosen as a reference to the novel ''[[Fahrenheit 451]]''. ==5xx Server error== The server failed to fulfill an apparently valid request.<ref>{{cite web|title=Server Error Codes|url=http://www.csgnetwork.com/servererrors.html|website=CSGNetwork.com|accessdate=16 October 2015}}</ref> Response status codes beginning with the digit "5" indicate cases in which the server is aware that it has encountered an error or is otherwise incapable of performing the request. Except when responding to a HEAD request, the server ''should'' include an entity containing an explanation of the error situation, and indicate whether it is a temporary or permanent condition. Likewise, user agents ''should'' display any included entity to the user. These response codes are applicable to any request method.<ref>{{cite web|last1=mrGott|title=HTTP Status Codes To Handle Errors In Your API|url=http://blog.mrgott.com/misc/5-http-status-codes-to-handle-errors-in-your-api|website=mrGott|accessdate=16 October 2015}}</ref> ;{{anchor |500}}500 Internal Server Error : A generic error message, given when an unexpected condition was encountered and no more specific message is suitable.<ref>{{cite web|last1=Fisher|first1=Tim|title=500 Internal Server Error|url=https://www.lifewire.com/500-internal-server-error-explained-2622938|website=Lifewire|accessdate=22 February 2017}}</ref> ;{{anchor |501}}501 Not Implemented : The server either does not recognize the request method, or it lacks the ability to fulfill the request. Usually this implies future availability (e.g., a new feature of a web-service API).<ref>{{cite web|title=HTTP Error 501 Not implemented|url=http://www.checkupdown.com/status/E501.html|website=Check Up Down|accessdate=22 February 2017}}</ref> ;{{anchor |502}}502 Bad Gateway : The server was acting as a [[gateway (telecommunications)|gateway]] or proxy and received an invalid response from the upstream server.<ref>{{cite web|last1=Fisher|first1=Tim|title=502 Bad Gateway|url=https://www.lifewire.com/502-bad-gateway-error-explained-2622939|website=Lifewire|accessdate=22 February 2017}}</ref> ;{{anchor |503}}503 Service Unavailable : The server is currently unavailable (because it is overloaded or down for maintenance). Generally, this is a temporary state.<ref>{{cite web|last1=alex|title=What is the correct HTTP status code to send when a site is down for maintenance?|url=https://stackoverflow.com/questions/2786595/what-is-the-correct-http-status-code-to-send-when-a-site-is-down-for-maintenance|website=Stack Overflow|accessdate=16 October 2015}}</ref> ;{{anchor |504}}504 Gateway Time-out : The server was acting as a gateway or proxy and did not receive a timely response from the upstream server.<ref>{{cite web|title=HTTP Error 504 Gateway timeout|url=http://www.checkupdown.com/status/E504.html|website=Check Up Down|accessdate=16 October 2015}}</ref> ;{{anchor |505}}505 HTTP Version Not Supported : The server does not support the HTTP protocol version used in the request.<ref>{{cite web|title=HTTP Error 505 - HTTP version not supported|url=http://www.checkupdown.com/status/E505.html|website=Check Up Down|accessdate=16 October 2015}}</ref> ;{{anchor |506}}506 Variant Also Negotiates (RFC 2295) : Transparent [[content negotiation]] for the request results in a [[circular reference]].<ref name="RFC_2295">{{cite IETF | title = Transparent Content Negotiation in HTTP | rfc = 2295 | last1 = Holtman | first1 = Koen | authorlink1 = | last2 = Mutz | first2 = Andrew H. | authorlink2 = | year = 1998 | month = March | publisher = [[Internet Engineering Task Force|IETF]] | accessdate = October 24, 2009 }}</ref> ;{{anchor |507}}507 Insufficient Storage (WebDAV; RFC 4918) : The server is unable to store the representation needed to complete the request.<ref name="RFC_4918"/> ;{{anchor |508}}508 Loop Detected (WebDAV; RFC 5842) : The server detected an infinite loop while processing the request (sent in lieu of [[#208|208 Already Reported]]). ;{{anchor |510}}510 Not Extended (RFC 2774) : Further extensions to the request are required for the server to fulfill it.<ref name="RFC_2774">{{cite IETF | title = An HTTP Extension Framework | rfc = 2774 | last1 = Nielsen | first1 = Henrik Frystyk | authorlink1 = Henrik Frystyk Nielsen | last2 = Leach | first2 = Paul | authorlink2 = | last3 = Lawrence | first3 = Scott | authorlink3 = | year = 2000 | month = February | publisher = [[Internet Engineering Task Force|IETF]] | accessdate = October 24, 2009 }}</ref> ;{{anchor|511}}511 Network Authentication Required (RFC 6585) :The client needs to authenticate to gain network access. Intended for use by intercepting proxies used to control access to the network (e.g., "[[captive portal]]s" used to require agreement to Terms of Service before granting full Internet access via a [[Hotspot (Wi-Fi)|Wi-Fi hotspot]]).<ref name="rfc6585"/> :{{Anchor|unofficial}} ==Unofficial codes== The following codes are not specified by any standard. ;103 Checkpoint :Used in the resumable requests proposal to resume aborted PUT or POST requests.<ref>{{cite web |url=http://code.google.com/p/gears/wiki/ResumableHttpRequestsProposal |title=ResumableHttpRequestsProposal |archive-url=http://web.archive.org/web/20151013212135/http://code.google.com/p/gears/wiki/ResumableHttpRequestsProposal |archive-date=2015-10-13 |access-date= 2017-03-08}}</ref> ;103 Early Hints :Used to return some response headers before entire HTTP response.<ref>{{cite web|url=https://tools.ietf.org/html/draft-kazuho-early-hints-status-code-00|title=draft-kazuho-early-hints-status-code-00 - An HTTP status code for Indicating Hints|last=Oku|first=Kazuho|date=2016-10-31|website=IETF Tools|access-date=2016-11-26}}</ref><ref>{{cite web|url=http://www.slideshare.net/kazuho/reorganizing-website-architecture-for-http2-and-beyond|title=Reorganizing Website Architecture for HTTP/2 and Beyond|last=Oku|first=Kazuho|date=2016-11-08|website=SlideShare|access-date=2016-11-26}}</ref> ;{{anchor |420}}420 Method Failure ([[Spring Framework]]) :A deprecated response used by the Spring Framework when a method has failed.<ref>{{cite web|title=Enum HttpStatus|url=https://docs.spring.io/spring/docs/current/javadoc-api/org/springframework/http/HttpStatus.html|website=Spring Framework|publisher=org.springframework.http|accessdate=16 October 2015}}</ref> ;420 Enhance Your Calm ([[Twitter]]) :Returned by version 1 of the Twitter Search and Trends API when the client is being rate limited; versions 1.1 and later use the [[#429|429 Too Many Requests]] response code instead.<ref name="TwitterErrorCodes">{{cite web| url = https://dev.twitter.com/docs/error-codes-responses | title = Twitter Error Codes & Responses | year = 2014 | publisher=[[Twitter]] | accessdate=January 20, 2014}}</ref> ;{{anchor|450}}450 Blocked by Windows Parental Controls (Microsoft) :The Microsoft extension code indicated when Windows Parental Controls are turned on and are blocking access to the given webpage.<ref>{{cite web | url = https://public.bn1.livefilestore.com/y1pJXeg_sNOONKwMraE-xmZFWAfZF6COAKnyfgc-2ykUof743pV4XuRqm14pj-b_yK8Km4sfSR6mU5OhLrupZ8dFg | title = Screenshot of error page | format = bmp |accessdate = October 11, 2009}}</ref> ;{{anchor |498}}498 Invalid Token (Esri) :Returned by [[ArcGIS Server|ArcGIS for Server]]. Code 498 indicates an expired or otherwise invalid token.<ref name="arcgis">{{cite web | url = http://help.arcgis.com/en/arcgisserver/10.0/apis/soap/index.htm#Using_token_authentication.htm | title = Using token-based authentication |website = ArcGIS Server SOAP SDK}}</ref> ;499 Token Required (Esri) :Returned by [[ArcGIS Server|ArcGIS for Server]]. Code 499 indicates that a token is required but was not submitted.<ref name="arcgis" /> ;{{anchor|509}}509 Bandwidth Limit Exceeded ([[Apache Web Server]]/[[cPanel]]) :The server has exceeded the bandwidth specified by the server administrator; this is often used by shared hosting providers to limit the bandwidth of customers.<ref>{{cite web|url=https://documentation.cpanel.net/display/CKB/HTTP+Error+Codes+and+Quick+Fixes#HTTPErrorCodesandQuickFixes-509BandwidthLimitExceeded|title=HTTP Error Codes and Quick Fixes|publisher=Docs.cpanel.net|accessdate=October 15, 2015}}</ref> ;{{anchor |530}}530 Site is frozen :Used by the [[Pantheon (software)|Pantheon]] web platform to indicate a site that has been frozen due to inactivity.<ref>{{cite web |url=https://pantheon.io/docs/platform-considerations/ |title=Platform Considerations {{!}} Pantheon Docs |website=pantheon.io}}</ref> ;{{anchor |599}}598 (Informal convention) Network read timeout error :Used by some HTTP proxies to signal a network read timeout behind the proxy to a client in front of the proxy.<ref>{{Cite web|url=http://www.ascii-code.com/http-status-codes.php|title=HTTP status codes - ascii-code.com|last=http://www.injosoft.se|first=Injosoft AB,|website=www.ascii-code.com|access-date=2016-12-23}}</ref><ref>{{Cite web|url=http://www.ivoronline.com/Coding/Theory/HTTP/HTTP%20-%20Response%20-%20Codes%20-%20598%20Network%20read%20timeout%20error.php|title=HTTP - Response - Codes - 598 Network read timeout error|website=www.ivoronline.com|access-date=2016-12-23}}</ref> ;{{anchor |599}}599 (Informal convention) Network connect timeout error :Used to indicate when the connection to the network times out.<ref>{{Cite web|url=https://http.cat/599|title=599 Network connect timeout error|last=|first=|date=|website=http.cat|publisher=|access-date=November 17, 2016}}</ref> {{Citation needed|date=November 2016}} ===Internet Information Services=== The [[Internet Information Services]] expands the 4xx error space to signal errors with the client's request. ;{{anchor|440}}440 Login Time-out :The client's session has expired and must log in again.<ref name="MS_KB941201"> {{cite web| url = https://support.microsoft.com/en-us/help/941201/ | title = Error message when you try to log on to Exchange 2007 by using Outlook Web Access: "440 Login Time-out" | year = 2010 | publisher=[[Microsoft]] | accessdate=November 13, 2013 }}</ref> ;{{anchor |449}}449 Retry With :The server cannot honour the request because the user has not provided the required information.<ref name="MS_DD891478">{{cite web | url = http://msdn.microsoft.com/en-us/library/dd891478(PROT.10).aspx | title = 2.2.6 449 Retry With Status Code | year = 2009 | publisher=[[Microsoft]] | accessdate=October 26, 2009}}</ref> ;{{anchor|451-MS}}451 Redirect :Used in [[Exchange ActiveSync]] when either a more efficient server is available or the server cannot access the users' mailbox.<ref>{{cite web | title = MS-ASCMD, Section 3.1.5.2.2 | url = http://msdn.microsoft.com/en-us/library/gg651019 |publisher=Msdn.microsoft.com|accessdate=January 8, 2015 }}</ref> The client is expected to re-run the HTTP AutoDiscover operation to find a more appropriate server.<ref>{{cite web | title = Ms-oxdisco | url = http://msdn.microsoft.com/en-us/library/cc433481 |publisher=Msdn.microsoft.com|accessdate=January 8, 2015 }}</ref> ===nginx=== The [[nginx]] web server software expands the 4xx error space to signal issues with the client's request.<ref>{{cite web|url=http://lxr.nginx.org/source/src/http/ngx_http_request.h|title=ngx_http_request.h|work=nginx 1.9.5 source code|publisher=nginx inc.|accessdate=2016-01-09}}</ref><ref>{{cite web|url=http://lxr.nginx.org/source/src/http/ngx_http_special_response.c|title=ngx_http_special_response.c|work=nginx 1.9.5 source code|publisher=nginx inc.|accessdate=2016-01-09}}</ref> These are only used for logging purposes, no actual response is sent with these codes. ;{{anchor|444}}444 No Response :Used to indicate that the server has returned no information to the client and closed the connection. ;{{anchor|495}}495 SSL Certificate Error :An expansion of the [[#400|400 Bad Request]] response code, used when the client has provided an invalid [[client certificate]]. ;{{anchor|496}}496 SSL Certificate Required :An expansion of the [[#400|400 Bad Request]] response code, used when a client certificate is required but not provided. ;{{anchor|497}}497 HTTP Request Sent to HTTPS Port :An expansion of the [[#400|400 Bad Request]] response code, used when the client has made a HTTP request to a port listening for HTTPS requests. ;{{anchor|499}}499 Client Closed Request :Used when the client has closed the request before the server could send a response. ===Cloudflare=== [[Cloudflare]]'s reverse proxy service expands the 5xx series of errors space to signal issues with the origin server.<ref>{{cite web|url=https://support.cloudflare.com/hc/en-us/sections/200820298-Error-Pages|title=Troubleshooting: Error Pages|publisher=[[Cloudflare]]|accessdate=2016-01-09}}</ref> ;{{anchor|520}}520 Unknown Error :The 520 error is used as a "catch-all response for when the origin server returns something unexpected", listing connection resets, large headers, and empty or invalid responses as common triggers. ;{{anchor|521}}521 Web Server Is Down :The origin server has refused the connection from Cloudflare. ;{{anchor|522}}522 Connection Timed Out :Cloudflare could not negotiate a [[TCP handshake]] with the origin server. ;{{anchor|523}}523 Origin Is Unreachable :Cloudflare could not reach the origin server; for example, if the [[DNS record]]s for the origin server are incorrect. ;{{anchor|524}}524 A Timeout Occurred :Cloudflare was able to complete a TCP connection to the origin server, but did not receive a timely HTTP response. ;{{anchor|525}}525 SSL Handshake Failed :Cloudflare could not negotiate a [[Transport Layer Security#TLS handshake|SSL/TLS handshake]] with the origin server. ;{{anchor|526}}526 Invalid SSL Certificate :Cloudflare could not validate the SSL/TLS certificate that the origin server presented. ;{{anchor|527}}527 Railgun Error :Error 527 indicates that the requests timeout or failed after the WAN connection has been established.<ref>{{cite web|url=https://support.cloudflare.com/hc/en-us/articles/217891268-527-Railgun-Listener-to-Origin-Error|title=Railgun Listener to Origin Error|publisher=[[Cloudflare]]|accessdate=2016-10-12}}</ref> ==See also== * [[HTTP 404#Custom error pages|Custom error pages]] * [[List of FTP server return codes]] * [[List of HTTP header fields]] ==Notes== {{Reflist|group=note}} ==References== {{Reflist|2}} ==External links== {{commons category|Hypertext Transfer Protocol}} *[http://www.iana.org/assignments/http-status-codes/http-status-codes.xhtml Hypertext Transfer Protocol (HTTP) Status Code Registry] *Microsoft Knowledge Base: MSKB943891: [http://support.microsoft.com/kb/943891/ The HTTP status codes in IIS 7.0] *[http://www.getnetgoing.com/HTTP.html Help for HTTP errors] *[http://savanttools.com/test-http-status-codes Test any HTTP status code in a web browser] *[http://www.checkhttpstatuscodes.com Checking tool for URL for status code with description] *[http://www.serviceunavailable.info/ Real time server-side 503 HTTP status code checker tool] *[http://racksburg.com/choosing-an-http-status-code/ Choosing an HTTP Status Code — Stop Making It Hard] {{Error messages}} {{Use mdy dates|date=November 2012}} {{DEFAULTSORT:List Of Http status codes}} [[Category:Hypertext Transfer Protocol status codes| ]] [[Category:Internet-related lists|HTTP status codes]]'