List of HTTP status codes: Difference between revisions

From Wikipedia, the free encyclopedia
Browse history interactively
← Previous editNext edit →
Content deleted Content added
VisualWikitext
m Reverted edits by 81.17.92.95 to last revision by OrangeDog (HG)
Added {{cite IETF}} citation templates, Used <nowiki> where autolinking with MediaWiki:Rfcurl is not desired
Line 1: Line 1:
{{HTTP}}
{{HTTP}}
<!-- This article is in British English, in particular "fulfil" is correctly spelled. See [[WP:ENGVAR]] -->
<!-- This article is in British English, in particular "fulfil" is correctly spelled. See [[WP:ENGVAR]] -->
The following is a list of '''[[HyperText Transfer Protocol]] (HTTP) response status codes'''. This includes codes from [[IETF]] [[internet standard]]s as well as unstandardised [[Request for Comments|RFCs]], other specifications and some additional commonly used codes. The first digit of the status code specifies one of five classes of response; the bare minimum for an HTTP client is that it recognises these five classes. Microsoft [[Internet Information Services|IIS]] may use additional decimal sub-codes to provide more specific information,<ref name="IIS">{{cite web |url=http://support.microsoft.com/kb/943891/ |title=The HTTP status codes in IIS 7.0 |accessdate=2009-04-01}}</ref> but these are not listed here. The phrases used are the standard examples, but any human-readable alternative can be provided. Unless otherwise stated, the status code is part of the HTTP/1.1 standard.
The following is a list of '''[[HyperText Transfer Protocol]] (HTTP) response status codes'''. This includes codes from [[IETF]] [[internet standard]]s as well as unstandardised [[Request for Comments|RFCs]], other specifications and some additional commonly used codes. The first digit of the status code specifies one of five classes of response; the bare minimum for an HTTP client is that it recognises these five classes. Microsoft [[Internet Information Services|IIS]] may use additional decimal sub-codes to provide more specific information,<ref>{{cite web | url = http://support.microsoft.com/kb/943891/ | title = The HTTP status codes in IIS 7.0 | accessdate = 2009-04-01}}</ref> but these are not listed here. The phrases used are the standard examples, but any human-readable alternative can be provided. Unless otherwise stated, the status code is part of the HTTP/1.1 standard.


==1xx Informational==
==1xx Informational==
Request received, continuing process.
Request received, continuing process.<ref>{{cite IETF | rfc = 2616 | section = Informational 1xx | sectionnum = 10.1 | pages = 57{{ndash}} 58}}</ref>


This class of status code indicates a provisional response, consisting only of the Status-Line and optional headers, and is terminated by an empty line. Since HTTP/1.0 did not define any 1xx status codes, servers ''must not'' send a 1xx response to an HTTP/1.0 client except under experimental conditions.
This class of status code indicates a provisional response, consisting only of the Status-Line and optional headers, and is terminated by an empty line. Since HTTP/1.0 did not define any 1xx status codes, servers ''must not'' send a 1xx response to an HTTP/1.0 client except under experimental conditions.


; 100 Continue
; 100 Continue
:This means that the server has received the request headers, and that 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 [[Hypertext Transfer Protocol#Request methods|POST]] request). If the request body is large, sending it to a server when a request has already been rejected based upon inappropriate headers is inefficient. To have a server check if the request could be accepted based on the request's headers alone, a client must send <code>Expect: 100-continue</code> as a header in its initial request (see {{rfcurl|2616|section=14.20}}{{ndash}} Expect header) and check if a <code>100 Continue</code> status code is received in response before continuing (or receive <code>417 Expectation Failed</code> and not continue).<ref>{{rfcurl|2616|section=8.2.3}}{{ndash}} Use of the 100 (Continue) Status</ref>
: This means that the server has received the request headers, and that 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 [[Hypertext Transfer Protocol#Request methods|POST]] request). If the request body is large, sending it to a server when a request has already been rejected based upon inappropriate headers is inefficient. To have a server check if the request could be accepted based on the request's headers alone, a client must send <code>Expect: 100-continue</code> as a header in its initial request<ref>{{cite IETF | rfc = 2616 | section = Expect | sectionnum = 14.20 | pages = 126{{ndash}} 127}}</ref> and check if a <code>100 Continue</code> status code is received in response before continuing (or receive <code>417 Expectation Failed</code> and not continue).<ref>{{cite IETF | rfc = 2616 | section = Use of the 100 (Continue) Status | sectionnum = 8.2.3 | pages = 48{{ndash}} 50}}</ref>

; 101 Switching Protocols
; 101 Switching Protocols
:This means the requester has asked the server to switch protocols and the server is acknowledging that it will do so.<ref>[http://www.google.com/support/webmasters/bin/answer.py?hl=en&answer=40132 Google Help]{{ndash}} Google HTTP status codes</ref>
: This means the requester has asked the server to switch protocols and the server is acknowledging that it will do so.<ref>{{cite IETF | rfc = 2616 | section = 101 Switching Protocols | sectionnum = 10.1.2 | page = 58}}</ref>
; 102 Processing ([[WebDAV]]) (<nowiki>RFC 2518</nowiki>)

: As a WebDAV request may contain many sub-requests involving file operations, it may take 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>{{cite IETF | rfc = 2518 | section = 102 Processing | sectionnum = 10.1 | page = 59}}</ref> This prevents the client from timing out and assuming the request was lost.
; 102 Processing ([[WebDAV]]) ({{rfcurl|2518}})
:As a WebDAV request may contain many sub-requests involving file operations, it may take 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. This prevents the client from timing out and assuming the request was lost.


==2xx Success==
==2xx Success==
The action was successfully received, understood, and accepted.
The action was successfully received, understood, and accepted.<ref>{{cite IETF | rfc = 2616 | section = Successful 2xx | sectionnum = 10.2 | pages = 58{{ndash}} 61}}</ref>


This class of status code indicates that the client's request was successfully received, understood, and accepted.
This class of status code indicates that the client's request was successfully received, understood, and accepted.


; 200 OK
; 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.
: 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>{{cite IETF | rfc = 2616 | section = 200 OK | sectionnum = 10.2.1 | pages = 58{{ndash}} 59}}</ref>
; 201 Created
; 201 Created
: The request has been fulfilled and resulted in a new resource being created.
: The request has been fulfilled and resulted in a new resource being created.<ref>{{cite IETF | rfc = 2616 | section = 201 Created | sectionnum = 10.2.2 | page = 59}}</ref>
; 202 Accepted
; 202 Accepted
: The request has been accepted for processing, but the processing has not been completed. The request might or might not eventually be acted upon, as it might be disallowed when processing actually takes place.
: The request has been accepted for processing, but the processing has not been completed. The request might or might not eventually be acted upon, as it might be disallowed when processing actually takes place.<ref>{{cite IETF | rfc = 2616 | section = 202 Accepted | sectionnum = 10.2.3 | page = 59}}</ref>
; 203 Non-Authoritative Information (since HTTP/1.1)
; 203 Non-Authoritative Information (since HTTP/1.1)
: The server successfully processed the request, but is returning information that may be from another source.
: The server successfully processed the request, but is returning information that may be from another source.<ref>{{cite IETF | rfc = 2616 | section = 203 Non-Authoritative Information | sectionnum = 10.2.4 | page = 59}}</ref>
; 204 No Content
; 204 No Content
: The server successfully processed the request, but is not returning any content.
: The server successfully processed the request, but is not returning any content.<ref>{{cite IETF | rfc = 2616 | section = 204 No Content | sectionnum = 10.2.5 | page = 60}}</ref>
; 205 Reset Content
; 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.
: 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 IETF | rfc = 2616 | section = 205 Reset Content | sectionnum = 10.2.6 | page = 60}}</ref>
; 206 Partial Content
; 206 Partial Content
: The server is delivering only part of the resource due to a range header sent by the client. This is used by tools like [[wget]] to enable resuming of interrupted downloads, or split a download into multiple simultaneous streams.
: The server is delivering only part of the resource due to a range header sent by the client. This is used by tools like [[wget]] to enable resuming of interrupted downloads, or split a download into multiple simultaneous streams.<ref>{{cite IETF | rfc = 2616 | section = 206 Partial Content | sectionnum = 10.2.7 | pages = 60{{ndash}} 61}}</ref>
; 207 Multi-Status (WebDAV) ({{rfcurl|2518}})
; 207 Multi-Status (WebDAV) (<nowiki>RFC 2518</nowiki>)
: 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.
: 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>{{cite IETF | rfc = 2518 | section = Status Codes for use with 207 (Multi-Status) | sectionnum = 8.2.1 | page = 3}}</ref>


==3xx Redirection==
==3xx Redirection==
The client must take additional action to complete the request.
The client must take additional action to complete the request.<ref>{{cite IETF | rfc = 2616 | section = Redirection 3xx | sectionnum = 10.3 | page = 61}}</ref>


This class of status code indicates that further action needs to be taken by the user agent in order to fulfil the request. The action required ''may'' be carried out by the user agent without interaction with the user if and only if the method used in the second request is GET or HEAD. A user agent ''should not'' automatically redirect a request more than five times, since such redirections usually indicate an [[infinite loop]].
This class of status code indicates that further action needs to be taken by the user agent in order to fulfil the request. The action required ''may'' be carried out by the user agent without interaction with the user if and only if the method used in the second request is GET or HEAD. A user agent ''should not'' automatically redirect a request more than five times, since such redirections usually indicate an [[infinite loop]].


; 300 Multiple Choices
; 300 Multiple Choices
: Indicates multiple options for the resource that the client may follow. It, for instance, could be used to present different format options for video, list files with different [[file extensions|extensions]], or [[word sense disambiguation]].
: Indicates multiple options for the resource that the client may follow. It, for instance, could be used to present different format options for video, list files with different [[file extensions|extensions]], or [[word sense disambiguation]].<ref>{{cite IETF | rfc = 2616 | section = 300 Multiple Choices | sectionnum = 10.3.1 | pages = 61{{ndash}} 62}}</ref>
; [[HTTP 301|301 Moved Permanently]]
; [[HTTP 301|301 Moved Permanently]]
: This and all future requests should be directed to the given [[URI]].
: This and all future requests should be directed to the given [[URI]].<ref>{{cite IETF | rfc = 2616 | section = 301 Moved Permanently | sectionnum = 10.3.2 | page = 62}}</ref>
; [[HTTP 302|302 Found]]
; [[HTTP 302|302 Found]]
: This is the most popular redirect code{{Fact|date=February 2009}}, but also an example of industrial practice contradicting the standard. HTTP/1.0 specification ({{rfcurl|1945}}) required the client to perform a temporary redirect (the original describing phrase was "Moved Temporarily"), but popular browsers implemented it as a 303 See Other. Therefore, HTTP/1.1 added status codes 303 and 307 to distinguish between the two behaviours. However, the majority of Web applications and frameworks still use the 302 status code as if it were the 303.
: This is the most popular redirect code{{Fact|date=February 2009}}, but also an example of industrial practice contradicting the standard.<ref>{{cite IETF | rfc = 2616 | section = 302 Found | sectionnum = 10.3.3 | pages = 62{{ndash}} 63}}</ref> 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 302 moved temporarily">{{cite IETF | rfc = 1945 | section = 302 Moved Temporarily | page = 35}}</ref> but popular browsers implemented it as a 303 See Other.<ref name="rfc 1945 302 moved temporarily" /> Therefore, HTTP/1.1 added status codes 303 and 307 to distinguish between the two behaviours. However, the majority of Web applications and frameworks still use the 302 status code as if it were the 303.
; [[HTTP 303|303 See Other]] (since HTTP/1.1)
; [[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 PUT, it should be assumed that the server has received the data and the redirect should be issued with a separate GET message.
: The response to the request can be found under another [[Uniform Resource Identifier|URI]] using a GET method. When received in response to a PUT, it should be assumed that the server has received the data and the redirect should be issued with a separate GET message.<ref>{{cite IETF | rfc = 2616 | section = 303 See Other | sectionnum = 10.3.4 | page = 63}}</ref>
; 304 Not Modified
; 304 Not Modified
: Indicates the resource has not been modified since last requested. Typically, the HTTP client provides a header like the If-Modified-Since header to provide a time against which to compare. Utilizing this saves bandwidth and reprocessing on both the server and client, as only the header data must be sent and received in comparison to the entirety of the page being re-processed by the server, then resent using more bandwidth of the server and client.
: Indicates the resource has not been modified since last requested.<ref>{{cite IETF | rfc = 2616 | section = 304 Not Modified | sectionnum = 10.3.5 | pages = 63{{ndash}} 64}}</ref> Typically, the HTTP client provides a header like the If-Modified-Since header to provide a time against which to compare. Utilizing this saves bandwidth and reprocessing on both the server and client, as only the header data must be sent and received in comparison to the entirety of the page being re-processed by the server, then resent using more bandwidth of the server and client.
; 305 Use Proxy (since HTTP/1.1)
; 305 Use Proxy (since HTTP/1.1)
: 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 = 2003-03-03 | accessdate = 2009-05-21}}</ref> and [[Internet Explorer]]) do not correctly handle responses with this status code, primarily for security reasons.<ref>{{cite IETF | rfc = 2616 | section = 305 Use Proxy | sectionnum = 10.3.6 | page = 64}}</ref>
: 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
| accessdate = 2009-05-21
| date = 2003-03-03
}}</ref> and [[Internet Explorer]]) do not correctly handle responses with this status code, primarily for security reasons.
; 306 Switch Proxy
; 306 Switch Proxy
: No longer used.<ref>{{cite IETF | rfc = 2616 | section = 306 (Unused) | sectionnum = 10.3.7 | page = 64}}</ref>
: No longer used.
; 307 Temporary Redirect (since HTTP/1.1)
; 307 Temporary Redirect (since HTTP/1.1)
: In this occasion, the request should be repeated with another URI, but future requests can still use the original URI. In contrast to 303, the request method should not be changed when reissuing the original request. For instance, a POST request must be repeated using another POST request.
: In this occasion, the request should be repeated with another URI, but future requests can still use the original URI.<ref>{{cite IETF | rfc = 2616 | section = 307 Temporary Redirect | sectionnum = 10.3.8 | page = 65}}</ref> In contrast to 303, the request method should not be changed when reissuing the original request. For instance, a POST request must be repeated using another POST request.


==4xx Client Error==
==4xx Client Error==
The request contains bad syntax or cannot be fulfilled.
The request contains bad syntax or cannot be fulfilled.<ref>{{cite IETF | rfc = 2616 | section = Client Error 4xx | sectionnum = 10.4 | pages = 65{{ndash}} 70}}</ref>


The 4xx class of status code is intended for cases 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. These are typically the most common error codes encountered while online.
The 4xx class of status code is intended for cases 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. These are typically the most common error codes encountered while online.


; 400 Bad Request
; 400 Bad Request
: The request contains bad syntax or cannot be fulfilled.
: The request contains bad syntax or cannot be fulfilled.<ref>{{cite IETF | rfc = 2616 | section = 400 Bad Request | sectionnum = 10.4.1 | page = 65}}</ref>
; 401 Unauthorized
; 401 Unauthorized
: Similar to ''403 Forbidden'', but specifically for use when authentication is possible but has failed or 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]].
: Similar to ''403 Forbidden'', but specifically for use when authentication is possible but has failed or not yet been provided.<ref>{{cite IETF | rfc = 2616 | section = 401 Unauthorized | sectionnum = 10.4.2 | page = 66}}</ref> 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]].
; 402 Payment Required
; 402 Payment Required
: 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 has never been used.
: Reserved for future use.<ref>{{cite IETF | rfc = 2616 | section = 402 Payment Required | sectionnum = 10.4.3 | page = 66}}</ref> 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 has never been used.
; [[HTTP 403|403 Forbidden]]
; [[HTTP 403|403 Forbidden]]
: The request was a legal request, but the server is refusing to respond to it. Unlike a ''401 Unauthorized'' response, authenticating will make no difference.
: The request was a legal request, but the server is refusing to respond to it.<ref name="rfc 2612 10.4.4">{{cite IETF | rfc = 2616 | section = 403 Forbidden | sectionnum = 10.4.4 | page = 66}}</ref> Unlike a ''401 Unauthorized'' response, authenticating will make no difference.<ref name="rfc 2612 10.4.4" />
; [[HTTP 404|404 Not Found]]
; [[HTTP 404|404 Not Found]]
: The requested resource could not be found but may be available again in the future. Subsequent requests by the client are permissible.
: The requested resource could not be found but may be available again in the future.<ref>{{cite IETF | rfc = 2616 | section = 404 Not Found | sectionnum = 10.4.5 | page = 66}}</ref> Subsequent requests by the client are permissible.
; 405 Method Not Allowed
; 405 Method Not Allowed
: A request was made of a resource using a request method not supported by that resource; for example, using GET on a form which requires data to be presented via POST, or using PUT on a read-only resource.
: A request was made of a resource using a request method not supported by that resource;<ref>{{cite IETF | rfc = 2616 | section = 405 Method Not Allowed | sectionnum = 10.4.6 | page = 66}}</ref> for example, using GET on a form which requires data to be presented via POST, or using PUT on a read-only 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.
: The requested resource is only capable of generating content not acceptable according to the Accept headers sent in the request.<ref>{{cite IETF | rfc = 2616 | section = 406 Not Acceptable | sectionnum = 10.4.7 | page = 67}}</ref>
; 407 Proxy Authentication Required
; 407 Proxy Authentication Required<ref>{{cite IETF | rfc = 2616 | section = 407 Proxy Authentication Required | sectionnum = 10.4.8 | page = 67}}</ref>
; 408 Request Timeout
; 408 Request Timeout
: The server timed out waiting for the request.
: The server timed out waiting for the request.<ref>{{cite IETF | rfc = 2616 | section = 408 Request Timeout | sectionnum = 10.4.9 | page = 67}}</ref>
; 409 Conflict
; 409 Conflict
: Indicates that the request could not be processed because of conflict in the request, such as an [[edit conflict]].
: Indicates that the request could not be processed because of conflict in the request, such as an [[edit conflict]].<ref>{{cite IETF | rfc = 2616 | section = 409 Conflict | sectionnum = 10.4.10 | pages = 67{{ndash}} 68}}</ref>
; 410 Gone
; 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; however, it is not necessary to return this code and a ''404 Not Found'' can be issued instead. Upon receiving a 410 status code, the client should not request the resource again in the future. Clients such as search engines should remove the resource from their indexes.
: Indicates that the resource requested is no longer available and will not be available again.<ref>{{cite IETF | rfc = 2616 | section = 410 Gone | sectionnum = 10.4.11 | page = 68}}</ref> This should be used when a resource has been intentionally removed; however, it is not necessary to return this code and a ''404 Not Found'' can be issued instead. Upon receiving a 410 status code, the client should not request the resource again in the future. Clients such as search engines should remove the resource from their indexes.
; 411 Length Required
; 411 Length Required
: The request did not specify the length of its content, which is required by the requested resource.
: The request did not specify the length of its content, which is required by the requested resource.<ref>{{cite IETF | rfc = 2616 | section = 411 Length Required | sectionnum = 10.4.12 | page = 68}}</ref>
; 412 Precondition Failed
; 412 Precondition Failed
: The server does not meet one of the preconditions that the requester put on the request.
: The server does not meet one of the preconditions that the requester put on the request.<ref>{{cite IETF | rfc = 2616 | section = 412 Precondition Failed | sectionnum = 10.4.13 | page = 68}}</ref>
; 413 Request Entity Too Large
; 413 Request Entity Too Large
: The request is larger than the server is willing or able to process.
: The request is larger than the server is willing or able to process.<ref>{{cite IETF | rfc = 2616 | section = 413 Request Entity Too Large | sectionnum = 10.4.14 | page = 69}}</ref>
; 414 Request-URI Too Long
; 414 Request-URI Too Long
: The [[URI]] provided was too long for the server to process.
: The [[URI]] provided was too long for the server to process.<ref>{{cite IETF | rfc = 2616 | section = 414 Request-URI Too Long | sectionnum = 10.4.15 | pages = 69}}</ref>
; 415 Unsupported Media Type
; 415 Unsupported Media Type
: The request did not specify any [[Internet media type|media types]] that the server or resource supports. For example the client specified that an image resource should be served as [[Scalable Vector Graphics|image/svg+xml]], but the server cannot find a matching version of the image.
: The request did not specify any [[Internet media type|media types]] that the server or resource supports.<ref>{{cite IETF | rfc = 2616 | section = 415 Unsupported Media Type | sectionnum = 10.4.16 | page = 69}}</ref> For example the client specified that an image resource should be served as [[Scalable Vector Graphics|image/svg+xml]], but the server cannot find a matching version of the image.
; 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 (for example, if the client asked for a part of the file that lies beyond the end of the file).
: The client has asked for a portion of the file, but the server cannot supply that portion.<ref>{{cite IETF | rfc = 2616 | section = 416 Requested Range Not Satisfiable | sectionnum = 10.4.17 | page = 69}}</ref> For example, if the client asked for a part of the file that lies beyond the end of the file.
; 417 Expectation Failed
; 417 Expectation Failed
: The server cannot meet the requirements of the Expect request-header field.
: The server cannot meet the requirements of the Expect request-header field.<ref>{{cite IETF | rfc = 2616 | section = 417 Expectation Failed | sectionnum = 10.4.18 | page = 70}}</ref>
<!-- The following code is under discussion on the talk page. Please discuss there before removing this entry -->
<!-- The following code is under discussion on the talk page. Please discuss there before removing this entry -->
; 418 I'm a teapot
; 418 I'm a teapot
: The HTCPCP server is a teapot. The responding entity MAY be [[I'm a Little Teapot|short and stout]]. This code was defined as one of the traditional [[IETF]] [[April Fools' Day RFC|April Fools' jokes]], in [http://www.ietf.org/rfc/rfc2324.txt RFC 2324], ''[[Hyper Text Coffee Pot Control Protocol]]'', and is not expected to be implemented by actual HTTP servers.
: The HTCPCP server is a teapot.<ref name="rfc 2324 2.3.2">{{cite IETF | rfc = 2324 | section = 418 I'm a teapot | sectionnum = 2.3.2 | page = 5}}</ref> The responding entity MAY be [[I'm a Little Teapot|short and stout]].<ref name="rfc 2324 2.3.2" /> This code was defined as one of the traditional [[IETF]] [[April Fools' Day RFC|April Fools' jokes]], in <nowiki>RFC 2324</nowiki>, ''[[Hyper Text Coffee Pot Control Protocol]]'', and is not expected to be implemented by actual HTTP servers.
<!-- -->
<!-- -->
; 422 Unprocessable Entity (WebDAV) ({{rfcurl|4918}})
; 422 Unprocessable Entity (WebDAV) (<nowiki>RFC 4918</nowiki>)
: The request was well-formed but was unable to be followed due to semantic errors.
: The request was well-formed but was unable to be followed due to semantic errors.<ref>{{cite IETF | rfc = 4918 | section = 422 Unprocessable Entity | sectionnum = 11.2 | page = 78}}</ref>
; 423 Locked (WebDAV) ({{rfcurl|4918}})
; 423 Locked (WebDAV) (<nowiki>RFC 4918</nowiki>)
: The resource that is being accessed is locked
: The resource that is being accessed is locked<ref>{{cite IETF | rfc = 4918 | section = 423 Locked | sectionnum = 11.3 | page = 78}}</ref>
; 424 Failed Dependency (WebDAV) ({{rfcurl|4918}})
; 424 Failed Dependency (WebDAV) (<nowiki>RFC 4918</nowiki>)
: The request failed due to failure of a previous request (e.g. a PROPPATCH).
: The request failed due to failure of a previous request (e.g. a PROPPATCH).<ref>{{cite IETF | rfc = 4918 | section = 424 Failed Dependency | sectionnum = 11.4 | page = 79}}</ref>
; 425 Unordered Collection ({{rfcurl|3648}})
; 425 Unordered Collection (<nowiki>RFC 3648</nowiki>)
: Defined in drafts of [http://tools.ietf.org/html/draft-ietf-webdav-collection-protocol-04#section-5.3.2 WebDav Advanced Collections], but not present in "Web Distributed Authoring and Versioning (WebDAV) Ordered Collections Protocol".
: Defined in drafts of "WebDAV Advanced Collections Protocol",<ref>{{cite IETF | draft = draft-ietf-webdav-collection-protocol-04 | section = 425 Unordered Collection | sectionnum = 7.2 | page = 41}}</ref> but not present in "Web Distributed Authoring and Versioning (WebDAV) Ordered Collections Protocol".<ref>{{cite IETF | title = Web Distributed Authoring and Versioning (WebDAV) Ordered Collections Protocol | rfc = 3648}}</ref>
; 426 Upgrade Required ({{rfcurl|2817}})
; 426 Upgrade Required (<nowiki>RFC 2817</nowiki>)
: The client should switch to [[Transport Layer Security|TLS/1.0]].
: The client should switch to [[Transport Layer Security|TLS/1.0]].<ref>{{cite IETF | rfc = 2817 | section = Server Requested Upgrade to HTTP over TLS | sectionnum = 4 | page = 5}}</ref>
; 449 Retry With
; 449 Retry With
: A Microsoft extension. The request should be retried after doing the appropriate action.
: A Microsoft extension. The request should be retried after doing the appropriate action.
; 450 Blocked by Windows Parental Controls
; 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.<ref>{{cite |url=http://zfhb6a.bay.livefilestore.com/y1pKZJpcqDcSF9uKwaTmx301Ilr7cbJGN94HXCoHvPGwuwAlt5DA4ln0Y-F1WE6ZUC3URdiJdRe4hILTo87jWx2Yg |title=Screenshot of error page |format=bmp |accessdate=2009-10-11}}</ref>
: A Microsoft extension. This error is given when Windows Parental Controls are turned on and are blocking access to the given webpage.<ref>{{cite web | url = http://zfhb6a.bay.livefilestore.com/y1pKZJpcqDcSF9uKwaTmx301Ilr7cbJGN94HXCoHvPGwuwAlt5DA4ln0Y-F1WE6ZUC3URdiJdRe4hILTo87jWx2Yg | title = Screenshot of error page | format = bmp |accessdate = 2009-10-11}}</ref>


==5xx Server Error==
==5xx Server Error==
The server failed to fulfil an apparently valid request.
The server failed to fulfil an apparently valid request.<ref>{{cite IETF | rfc = 2616 | section = Server Error 5xx | sectionnum = 10.5 | pages = 70{{ndash}} 71}}</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.
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.


; 500 Internal Server Error
; 500 Internal Server Error
:A generic error message, given when no more specific message is suitable.
: A generic error message, given when no more specific message is suitable.<ref>{{cite IETF | rfc = 2616 | section = 500 Internal Server Error | sectionnum = 10.5.1 | page = 70}}</ref>
; 501 Not Implemented
; 501 Not Implemented
:The server either does not recognise the request method, or it lacks the ability to fulfil the request.
: The server either does not recognise the request method, or it lacks the ability to fulfil the request.<ref>{{cite IETF | rfc = 2616 | section = 501 Not Implemented | sectionnum = 10.5.2 | page = 70}}</ref>
; 502 Bad Gateway
; 502 Bad Gateway
: The server was acting as a gateway or proxy and received an invalid response from the downstream server.
: The server was acting as a gateway or proxy and received an invalid response from the downstream server.<ref>{{cite IETF | rfc = 2616 | section = 502 Bad Gateway | sectionnum = 10.5.3 | pages = 70}}</ref>
; 503 Service Unavailable
; 503 Service Unavailable
: The server is currently unavailable (because it is overloaded or down for maintenance). Generally, this is a temporary state.
: The server is currently unavailable (because it is overloaded or down for maintenance).<ref>{{cite IETF | rfc = 2616 | section = 503 Service Unavailable | sectionnum = 10.5.4 | page = 70}}</ref> Generally, this is a temporary state.
; 504 Gateway Timeout
; 504 Gateway Timeout
: The server was acting as a gateway or proxy and did not receive a timely request from the downstream server.
: The server was acting as a gateway or proxy and did not receive a timely request from the downstream server.<ref>{{cite IETF | rfc = 2616 | section = 504 Gateway Timeout | sectionnum = 10.5.5 | page = 71}}</ref>
; 505 HTTP Version Not Supported
; 505 HTTP Version Not Supported
: The server does not support the HTTP protocol version used in the request.
: The server does not support the HTTP protocol version used in the request.<ref>{{cite IETF | rfc = 2616 | section = 505 HTTP Version Not Supported | sectionnum = 10.5.6 | page = 71}}</ref>
; 506 Variant Also Negotiates ({{rfcurl|2295}})
; 506 Variant Also Negotiates (<nowiki>RFC 2295</nowiki>)
:Transparent [[content negotiation]] for the request, results in a [[circular reference]].
: Transparent [[content negotiation]] for the request, results in a [[circular reference]].<ref>{{cite IETF | rfc = 2295 | section = 506 Variant Also Negotiates | sectionnum = 8.1 | page = 25}}</ref>
; 507 Insufficient Storage (WebDAV) ({{rfcurl|4918}})
; 507 Insufficient Storage (WebDAV) (<nowiki>RFC 4918</nowiki>)<ref>{{cite IETF | rfc = 4918 | section = 507 Insufficient Storage | sectionnum = 11.5 | page = 79}}</ref>
; 509 Bandwidth Limit Exceeded (Apache bw/limited extension)
; 509 Bandwidth Limit Exceeded (Apache bw/limited extension)
: This status code, while used by many servers, is not specified in any RFCs.
: This status code, while used by many servers, is not specified in any RFCs.
; 510 Not Extended ({{rfcurl|2774}})
; 510 Not Extended (<nowiki>RFC 2774</nowiki>)
:Further extensions to the request are required for the server to fulfil it.
: Further extensions to the request are required for the server to fulfil it.<ref>{{cite IETF | rfc = 2774 | section = 510 Not Extended | sectionnum = 7 | page = 11}}</ref>


==See also==
==See also==
Line 156: Line 149:


==Notes==
==Notes==
{{reflist}}
{{reflist|3}}


==References==
==References==
* {{cite IETF
* {{rfcurl|2616|section=10}}{{ndash}} HTTP specification
| title = Hypertext Transfer Protocol -- HTTP/1.0
* {{rfcurl|4918|section=11}}{{ndash}} WebDAV specification
| rfc = 1945
* {{rfcurl|2817|section=4}}{{ndash}} TLS Upgrade within HTTP specification
| last1 = Berners-Lee
* {{rfcurl|2817|section=7.1}}{{ndash}} HTTP Status Code Registry
| 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
| accessdate = 2009-10-24
}}
* {{cite IETF
| title = Hypertext Transfer Protocol -- HTTP/1.1
| rfc = 2068
| last1 = Fielding
| first1 = Roy T.
| authorlink1 = Roy Fielding
| last2 = Gettys
| first2 = Jim
| authorlink2 = Jim Gettys
| last3 = Mogul
| first3 = Jeffrey C.
| authorlink3 =
| last4 = Nielsen
| first4 = Henrik Frystyk
| authorlink4 = Henrik Frystyk Nielsen
| last5 = Berners-Lee
| first5 = Tim
| authorlink5 = Tim Berners-Lee
| year = 1997
| month = January
| accessdate = 2009-10-24
}}
* {{cite IETF
| title = Hypertext Transfer Protocol -- HTTP/1.1
| rfc = 2616
| last1 = Fielding
| first1 = Roy T.
| authorlink1 = Roy Fielding
| last2 = Gettys
| first2 = James
| authorlink2 = Jim Gettys
| last3 = Mogul
| first3 = Jeffrey C.
| authorlink3 =
| last4 = Nielsen
| first4 = Henrik Frystyk
| authorlink4 = Henrik Frystyk Nielsen
| last5 = Masinter
| first5 = Larry
| authorlink5 =
| last6 = Leach
| first6 = Paul J.
| authorlink6 =
| last7 = Berners-Lee
| first7 = Tim
| authorlink7 = Tim Berners-Lee
| year = 1999
| month = June
| accessdate = 2009-10-24
}}
* {{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
| accessdate = 2009-10-24
}}
* {{cite IETF
| title = Hyper Text Coffee Pot Control Protocol (HTCPCP/1.0)
| rfc = 2324
| last = Masinter
| first = Larry
| authorlink =
| date = April 1, 1998
| accessdate = 2009-10-24
}}
* {{cite IETF
| title = An HTTP Extension Framework
| rfc = 2774
| last1 = Nielsen
| first1 = Henrik Frystyk
| authorlink1 = Henrik Frystyk Nielsen
| last2 = Leach
| first2 = Paul J.
| authorlink2 =
| last3 = Lawrence
| first3 = Scott
| authorlink3 =
| year = 2000
| month = February
| accessdate = 2009-10-24
}}
* {{cite IETF
| title = Upgrading to TLS Within HTTP/1.1
| rfc = 2817
| last1 = Khare
| first1 = Rohit
| authorlink1 = Rohit Khare
| last2 = Lawrence
| first2 = Scott
| authorlink2 =
| year = 2000
| month = May
| accessdate = 2009-10-24
}}
* {{cite IETF
| title = HTTP Extensions for Distributed Authoring -- WEBDAV
| rfc = 2518
| last1 = Goland
| first1 = Yaron
| 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
| accessdate = 2009-10-24
}}
* {{cite IETF
| title = WebDAV Advanced Collections Protocol
| draft = draft-ietf-webdav-collection-protocol-04
| last1 = Slein
| first1 = Judy
| authorlink1 =
| last2 = Whitehead
| first2 = Jim
| authorlink2 = Jim Whitehead (professor)
| last3 = Davis
| first3 = Jim
| authorlink3 =
| last4 = Clemm
| first4 = Geoffrey
| authorlink4 =
| last5 = Fay
| first5 = Chuck
| authorlink5 =
| last6 = Crawford
| first6 = Jason
| authorlink6 =
| last7 = Chihaya
| first7 = Tyson
| authorlink7 =
| date = June 18, 1999
| accessdate = 2009-10-24
}}
* {{cite IETF
| title = Web Distributed Authoring and Versioning (WebDAV) Ordered Collections Protocol
| rfc = 3648
| last1 = Whitehead
| first1 = Jim
| authorlink1 = Jim Whitehead (professor)
| editor-last = Reschke
| editor-first = Julian F.
| editor-link =
| year = 2003
| month = December
| accessdate = 2009-10-24
}}
* {{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
| accessdate = 2009-10-24
}}
* [http://www.iana.org/assignments/http-status-codes IANA registry]
* [http://www.iana.org/assignments/http-status-codes IANA registry]
* [http://support.microsoft.com/kb/943891/ Microsoft Internet Information Services Status Codes and Sub-Codes]
* [http://support.microsoft.com/kb/943891/ Microsoft Internet Information Services Status Codes and Sub-Codes]
* [http://livedocs.adobe.com/fms/2/docs/00000338.html Adobe Flash status code definitions (i.e. 408)]
* [http://livedocs.adobe.com/fms/2/docs/00000338.html Adobe Flash status code definitions (i.e. 408)]
* [http://www.google.com/support/webmasters/bin/answer.py?hl=en&answer=40132 Google Help: HTTP status codes]
* {{rfcurl|2324}}{{ndash}} Hyper Text Coffee Pot Control Protocol (HTCPCP/1.0)


[[Category:HTTP]]
[[Category:HTTP]]

Revision as of 16:05, 24 October 2009

HTTP
Request methods
Header fields
Response status codes
Security access control methods
Security vulnerabilities

The following is a list of HyperText Transfer Protocol (HTTP) response status codes. This includes codes from IETF internet standards as well as unstandardised RFCs, other specifications and some additional commonly used codes. The first digit of the status code specifies one of five classes of response; the bare minimum for an HTTP client is that it recognises these five classes. Microsoft IIS may use additional decimal sub-codes to provide more specific information,[1] but these are not listed here. The phrases used are the standard examples, but any human-readable alternative can be provided. Unless otherwise stated, the status code is part of the HTTP/1.1 standard.

1xx Informational

Request received, continuing process.[2]

This class of status code indicates a provisional response, consisting only of the Status-Line and optional headers, and is terminated by an empty line. Since HTTP/1.0 did not define any 1xx status codes, servers must not send a 1xx response to an HTTP/1.0 client except under experimental conditions.

100 Continue
This means that the server has received the request headers, and that 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 request). If the request body is large, sending it to a server when a request has already been rejected based upon inappropriate headers is inefficient. To have a server check if the request could be accepted based on the request's headers alone, a client must send Expect: 100-continue as a header in its initial request[3] and check if a 100 Continue status code is received in response before continuing (or receive 417 Expectation Failed and not continue).[4]
101 Switching Protocols
This means the requester has asked the server to switch protocols and the server is acknowledging that it will do so.[5]
102 Processing (WebDAV) (RFC 2518)
As a WebDAV request may contain many sub-requests involving file operations, it may take 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.[6] This prevents the client from timing out and assuming the request was lost.

2xx Success

The action was successfully received, understood, and accepted.[7]

This class of status code indicates that the client's request was successfully received, understood, and accepted.

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.[8]
201 Created
The request has been fulfilled and resulted in a new resource being created.[9]
202 Accepted
The request has been accepted for processing, but the processing has not been completed. The request might or might not eventually be acted upon, as it might be disallowed when processing actually takes place.[10]
203 Non-Authoritative Information (since HTTP/1.1)
The server successfully processed the request, but is returning information that may be from another source.[11]
204 No Content
The server successfully processed the request, but is not returning any content.[12]
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.[13]
206 Partial Content
The server is delivering only part of the resource due to a range header sent by the client. This is used by tools like wget to enable resuming of interrupted downloads, or split a download into multiple simultaneous streams.[14]
207 Multi-Status (WebDAV) (RFC 2518)
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.[15]

3xx Redirection

The client must take additional action to complete the request.[16]

This class of status code indicates that further action needs to be taken by the user agent in order to fulfil the request. The action required may be carried out by the user agent without interaction with the user if and only if the method used in the second request is GET or HEAD. A user agent should not automatically redirect a request more than five times, since such redirections usually indicate an infinite loop.

300 Multiple Choices
Indicates multiple options for the resource that the client may follow. It, for instance, could be used to present different format options for video, list files with different extensions, or word sense disambiguation.[17]
301 Moved Permanently
This and all future requests should be directed to the given URI.[18]
302 Found
This is the most popular redirect code[citation needed], but also an example of industrial practice contradicting the standard.[19] HTTP/1.0 specification (RFC 1945) required the client to perform a temporary redirect (the original describing phrase was "Moved Temporarily"),[20] but popular browsers implemented it as a 303 See Other.[20] Therefore, HTTP/1.1 added status codes 303 and 307 to distinguish between the two behaviours. However, the majority of Web applications and frameworks still use the 302 status code as if it were the 303.
303 See Other (since HTTP/1.1)
The response to the request can be found under another URI using a GET method. When received in response to a PUT, it should be assumed that the server has received the data and the redirect should be issued with a separate GET message.[21]
304 Not Modified
Indicates the resource has not been modified since last requested.[22] Typically, the HTTP client provides a header like the If-Modified-Since header to provide a time against which to compare. Utilizing this saves bandwidth and reprocessing on both the server and client, as only the header data must be sent and received in comparison to the entirety of the page being re-processed by the server, then resent using more bandwidth of the server and client.
305 Use Proxy (since HTTP/1.1)
Many HTTP clients (such as Mozilla[23] and Internet Explorer) do not correctly handle responses with this status code, primarily for security reasons.[24]
306 Switch Proxy
No longer used.[25]
307 Temporary Redirect (since HTTP/1.1)
In this occasion, the request should be repeated with another URI, but future requests can still use the original URI.[26] In contrast to 303, the request method should not be changed when reissuing the original request. For instance, a POST request must be repeated using another POST request.

4xx Client Error

The request contains bad syntax or cannot be fulfilled.[27]

The 4xx class of status code is intended for cases 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. These are typically the most common error codes encountered while online.

400 Bad Request
The request contains bad syntax or cannot be fulfilled.[28]
401 Unauthorized
Similar to 403 Forbidden, but specifically for use when authentication is possible but has failed or not yet been provided.[29] 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.
402 Payment Required
Reserved for future use.[30] 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 has never been used.
403 Forbidden
The request was a legal request, but the server is refusing to respond to it.[31] Unlike a 401 Unauthorized response, authenticating will make no difference.[31]
404 Not Found
The requested resource could not be found but may be available again in the future.[32] Subsequent requests by the client are permissible.
405 Method Not Allowed
A request was made of a resource using a request method not supported by that resource;[33] for example, using GET on a form which requires data to be presented via POST, or using PUT on a read-only resource.
406 Not Acceptable
The requested resource is only capable of generating content not acceptable according to the Accept headers sent in the request.[34]
407 Proxy Authentication Required[35]
408 Request Timeout
The server timed out waiting for the request.[36]
409 Conflict
Indicates that the request could not be processed because of conflict in the request, such as an edit conflict.[37]
410 Gone
Indicates that the resource requested is no longer available and will not be available again.[38] This should be used when a resource has been intentionally removed; however, it is not necessary to return this code and a 404 Not Found can be issued instead. Upon receiving a 410 status code, the client should not request the resource again in the future. Clients such as search engines should remove the resource from their indexes.
411 Length Required
The request did not specify the length of its content, which is required by the requested resource.[39]
412 Precondition Failed
The server does not meet one of the preconditions that the requester put on the request.[40]
413 Request Entity Too Large
The request is larger than the server is willing or able to process.[41]
414 Request-URI Too Long
The URI provided was too long for the server to process.[42]
415 Unsupported Media Type
The request did not specify any media types that the server or resource supports.[43] For example the client specified that an image resource should be served as image/svg+xml, but the server cannot find a matching version of the image.
416 Requested Range Not Satisfiable
The client has asked for a portion of the file, but the server cannot supply that portion.[44] For example, if the client asked for a part of the file that lies beyond the end of the file.
417 Expectation Failed
The server cannot meet the requirements of the Expect request-header field.[45]
418 I'm a teapot
The HTCPCP server is a teapot.[46] The responding entity MAY be short and stout.[46] This code was defined 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.
422 Unprocessable Entity (WebDAV) (RFC 4918)
The request was well-formed but was unable to be followed due to semantic errors.[47]
423 Locked (WebDAV) (RFC 4918)
The resource that is being accessed is locked[48]
424 Failed Dependency (WebDAV) (RFC 4918)
The request failed due to failure of a previous request (e.g. a PROPPATCH).[49]
425 Unordered Collection (RFC 3648)
Defined in drafts of "WebDAV Advanced Collections Protocol",[50] but not present in "Web Distributed Authoring and Versioning (WebDAV) Ordered Collections Protocol".[51]
426 Upgrade Required (RFC 2817)
The client should switch to TLS/1.0.[52]
449 Retry With
A Microsoft extension. The request should be retried after doing 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.[53]

5xx Server Error

The server failed to fulfil an apparently valid request.[54]

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.

500 Internal Server Error
A generic error message, given when no more specific message is suitable.[55]
501 Not Implemented
The server either does not recognise the request method, or it lacks the ability to fulfil the request.[56]
502 Bad Gateway
The server was acting as a gateway or proxy and received an invalid response from the downstream server.[57]
503 Service Unavailable
The server is currently unavailable (because it is overloaded or down for maintenance).[58] Generally, this is a temporary state.
504 Gateway Timeout
The server was acting as a gateway or proxy and did not receive a timely request from the downstream server.[59]
505 HTTP Version Not Supported
The server does not support the HTTP protocol version used in the request.[60]
506 Variant Also Negotiates (RFC 2295)
Transparent content negotiation for the request, results in a circular reference.[61]
507 Insufficient Storage (WebDAV) (RFC 4918)[62]
509 Bandwidth Limit Exceeded (Apache bw/limited extension)
This status code, while used by many servers, is not specified in any RFCs.
510 Not Extended (RFC 2774)
Further extensions to the request are required for the server to fulfil it.[63]

See also

Notes

  1. ^ "The HTTP status codes in IIS 7.0". Retrieved 2009-04-01.
  2. ^ 1xx RFC 2616. pp. 57– 58. sec. Informational 1xx. doi:10.17487/RFC2616. {{citation}}: Check |url= value (help); Unknown parameter |sectionnum= ignored (help)
  3. ^ RFC 2616. pp. 126– 127. sec. Expect. doi:10.17487/RFC2616. {{citation}}: Unknown parameter |sectionnum= ignored (help)
  4. ^ of the 100 (Continue) Status RFC 2616. pp. 48– 50. sec. Use of the 100 (Continue) Status. doi:10.17487/RFC2616. {{citation}}: Check |url= value (help); Unknown parameter |sectionnum= ignored (help)
  5. ^ Switching Protocols RFC 2616. p. 58. sec. 101 Switching Protocols. doi:10.17487/RFC2616. {{citation}}: Check |url= value (help); Unknown parameter |sectionnum= ignored (help)
  6. ^ Processing RFC 2518. p. 59. sec. 102 Processing. doi:10.17487/RFC2518. {{citation}}: Check |url= value (help); Unknown parameter |sectionnum= ignored (help)
  7. ^ 2xx RFC 2616. pp. 58– 61. sec. Successful 2xx. doi:10.17487/RFC2616. {{citation}}: Check |url= value (help); Unknown parameter |sectionnum= ignored (help)
  8. ^ OK RFC 2616. pp. 58– 59. sec. 200 OK. doi:10.17487/RFC2616. {{citation}}: Check |url= value (help); Unknown parameter |sectionnum= ignored (help)
  9. ^ Created RFC 2616. p. 59. sec. 201 Created. doi:10.17487/RFC2616. {{citation}}: Check |url= value (help); Unknown parameter |sectionnum= ignored (help)
  10. ^ Accepted RFC 2616. p. 59. sec. 202 Accepted. doi:10.17487/RFC2616. {{citation}}: Check |url= value (help); Unknown parameter |sectionnum= ignored (help)
  11. ^ Non-Authoritative Information RFC 2616. p. 59. sec. 203 Non-Authoritative Information. doi:10.17487/RFC2616. {{citation}}: Check |url= value (help); Unknown parameter |sectionnum= ignored (help)
  12. ^ No Content RFC 2616. p. 60. sec. 204 No Content. doi:10.17487/RFC2616. {{citation}}: Check |url= value (help); Unknown parameter |sectionnum= ignored (help)
  13. ^ Reset Content RFC 2616. p. 60. sec. 205 Reset Content. doi:10.17487/RFC2616. {{citation}}: Check |url= value (help); Unknown parameter |sectionnum= ignored (help)
  14. ^ Partial Content RFC 2616. pp. 60– 61. sec. 206 Partial Content. doi:10.17487/RFC2616. {{citation}}: Check |url= value (help); Unknown parameter |sectionnum= ignored (help)
  15. ^ Codes for use with 207 (Multi-Status) RFC 2518. p. 3. sec. Status Codes for use with 207 (Multi-Status). doi:10.17487/RFC2518. {{citation}}: Check |url= value (help); Unknown parameter |sectionnum= ignored (help)
  16. ^ 3xx RFC 2616. p. 61. sec. Redirection 3xx. doi:10.17487/RFC2616. {{citation}}: Check |url= value (help); Unknown parameter |sectionnum= ignored (help)
  17. ^ Multiple Choices RFC 2616. pp. 61– 62. sec. 300 Multiple Choices. doi:10.17487/RFC2616. {{citation}}: Check |url= value (help); Unknown parameter |sectionnum= ignored (help)
  18. ^ Moved Permanently RFC 2616. p. 62. sec. 301 Moved Permanently. doi:10.17487/RFC2616. {{citation}}: Check |url= value (help); Unknown parameter |sectionnum= ignored (help)
  19. ^ Found RFC 2616. pp. 62– 63. sec. 302 Found. doi:10.17487/RFC2616. {{citation}}: Check |url= value (help); Unknown parameter |sectionnum= ignored (help)
  20. ^ a b Moved Temporarily RFC 1945. p. 35. sec. 302 Moved Temporarily. doi:10.17487/RFC1945. {{citation}}: Check |url= value (help)
  21. ^ See Other RFC 2616. p. 63. sec. 303 See Other. doi:10.17487/RFC2616. {{citation}}: Check |url= value (help); Unknown parameter |sectionnum= ignored (help)
  22. ^ Not Modified RFC 2616. pp. 63– 64. sec. 304 Not Modified. doi:10.17487/RFC2616. {{citation}}: Check |url= value (help); Unknown parameter |sectionnum= ignored (help)
  23. ^ "Mozilla Bugzilla Bug 187996: Strange behavior on 305 redirect". 2003-03-03. Retrieved 2009-05-21.
  24. ^ Use Proxy RFC 2616. p. 64. sec. 305 Use Proxy. doi:10.17487/RFC2616. {{citation}}: Check |url= value (help); Unknown parameter |sectionnum= ignored (help)
  25. ^ (Unused) RFC 2616. p. 64. sec. 306 (Unused). doi:10.17487/RFC2616. {{citation}}: Check |url= value (help); Unknown parameter |sectionnum= ignored (help)
  26. ^ Temporary Redirect RFC 2616. p. 65. sec. 307 Temporary Redirect. doi:10.17487/RFC2616. {{citation}}: Check |url= value (help); Unknown parameter |sectionnum= ignored (help)
  27. ^ Error 4xx RFC 2616. pp. 65– 70. sec. Client Error 4xx. doi:10.17487/RFC2616. {{citation}}: Check |url= value (help); Unknown parameter |sectionnum= ignored (help)
  28. ^ Bad Request RFC 2616. p. 65. sec. 400 Bad Request. doi:10.17487/RFC2616. {{citation}}: Check |url= value (help); Unknown parameter |sectionnum= ignored (help)
  29. ^ Unauthorized RFC 2616. p. 66. sec. 401 Unauthorized. doi:10.17487/RFC2616. {{citation}}: Check |url= value (help); Unknown parameter |sectionnum= ignored (help)
  30. ^ Payment Required RFC 2616. p. 66. sec. 402 Payment Required. doi:10.17487/RFC2616. {{citation}}: Check |url= value (help); Unknown parameter |sectionnum= ignored (help)
  31. ^ a b Forbidden RFC 2616. p. 66. sec. 403 Forbidden. doi:10.17487/RFC2616. {{citation}}: Check |url= value (help); Unknown parameter |sectionnum= ignored (help)
  32. ^ Not Found RFC 2616. p. 66. sec. 404 Not Found. doi:10.17487/RFC2616. {{citation}}: Check |url= value (help); Unknown parameter |sectionnum= ignored (help)
  33. ^ Method Not Allowed RFC 2616. p. 66. sec. 405 Method Not Allowed. doi:10.17487/RFC2616. {{citation}}: Check |url= value (help); Unknown parameter |sectionnum= ignored (help)
  34. ^ Not Acceptable RFC 2616. p. 67. sec. 406 Not Acceptable. doi:10.17487/RFC2616. {{citation}}: Check |url= value (help); Unknown parameter |sectionnum= ignored (help)
  35. ^ Proxy Authentication Required RFC 2616. p. 67. sec. 407 Proxy Authentication Required. doi:10.17487/RFC2616. {{citation}}: Check |url= value (help); Unknown parameter |sectionnum= ignored (help)
  36. ^ Request Timeout RFC 2616. p. 67. sec. 408 Request Timeout. doi:10.17487/RFC2616. {{citation}}: Check |url= value (help); Unknown parameter |sectionnum= ignored (help)
  37. ^ Conflict RFC 2616. pp. 67– 68. sec. 409 Conflict. doi:10.17487/RFC2616. {{citation}}: Check |url= value (help); Unknown parameter |sectionnum= ignored (help)
  38. ^ Gone RFC 2616. p. 68. sec. 410 Gone. doi:10.17487/RFC2616. {{citation}}: Check |url= value (help); Unknown parameter |sectionnum= ignored (help)
  39. ^ Length Required RFC 2616. p. 68. sec. 411 Length Required. doi:10.17487/RFC2616. {{citation}}: Check |url= value (help); Unknown parameter |sectionnum= ignored (help)
  40. ^ Precondition Failed RFC 2616. p. 68. sec. 412 Precondition Failed. doi:10.17487/RFC2616. {{citation}}: Check |url= value (help); Unknown parameter |sectionnum= ignored (help)
  41. ^ Request Entity Too Large RFC 2616. p. 69. sec. 413 Request Entity Too Large. doi:10.17487/RFC2616. {{citation}}: Check |url= value (help); Unknown parameter |sectionnum= ignored (help)
  42. ^ Request-URI Too Long RFC 2616. pp. 69. sec. 414 Request-URI Too Long. doi:10.17487/RFC2616. {{citation}}: Check |url= value (help); Unknown parameter |sectionnum= ignored (help)
  43. ^ Unsupported Media Type RFC 2616. p. 69. sec. 415 Unsupported Media Type. doi:10.17487/RFC2616. {{citation}}: Check |url= value (help); Unknown parameter |sectionnum= ignored (help)
  44. ^ Requested Range Not Satisfiable RFC 2616. p. 69. sec. 416 Requested Range Not Satisfiable. doi:10.17487/RFC2616. {{citation}}: Check |url= value (help); Unknown parameter |sectionnum= ignored (help)
  45. ^ Expectation Failed RFC 2616. p. 70. sec. 417 Expectation Failed. doi:10.17487/RFC2616. {{citation}}: Check |url= value (help); Unknown parameter |sectionnum= ignored (help)
  46. ^ a b I'm a teapot RFC 2324. p. 5. sec. 418 I'm a teapot. doi:10.17487/RFC2324. {{citation}}: Check |url= value (help); Unknown parameter |sectionnum= ignored (help)
  47. ^ Unprocessable Entity RFC 4918. p. 78. sec. 422 Unprocessable Entity. doi:10.17487/RFC4918. {{citation}}: Check |url= value (help); Unknown parameter |sectionnum= ignored (help)
  48. ^ Locked RFC 4918. p. 78. sec. 423 Locked. doi:10.17487/RFC4918. {{citation}}: Check |url= value (help); Unknown parameter |sectionnum= ignored (help)
  49. ^ Failed Dependency RFC 4918. p. 79. sec. 424 Failed Dependency. doi:10.17487/RFC4918. {{citation}}: Check |url= value (help); Unknown parameter |sectionnum= ignored (help)
  50. ^ Unordered Collection I-D draft-ietf-webdav-collection-protocol-04. p. 41. sec. 425 Unordered Collection. {{citation}}: Check |url= value (help); Unknown parameter |sectionnum= ignored (help)
  51. ^ Web Distributed Authoring and Versioning (WebDAV) Ordered Collections Protocol. doi:10.17487/RFC3648. RFC 3648.
  52. ^ Requested Upgrade to HTTP over TLS RFC 2817. p. 5. sec. Server Requested Upgrade to HTTP over TLS. doi:10.17487/RFC2817. {{citation}}: Check |url= value (help); Unknown parameter |sectionnum= ignored (help)
  53. ^ "Screenshot of error page" (bmp). Retrieved 2009-10-11.
  54. ^ Error 5xx RFC 2616. pp. 70– 71. sec. Server Error 5xx. doi:10.17487/RFC2616. {{citation}}: Check |url= value (help); Unknown parameter |sectionnum= ignored (help)
  55. ^ Internal Server Error RFC 2616. p. 70. sec. 500 Internal Server Error. doi:10.17487/RFC2616. {{citation}}: Check |url= value (help); Unknown parameter |sectionnum= ignored (help)
  56. ^ Not Implemented RFC 2616. p. 70. sec. 501 Not Implemented. doi:10.17487/RFC2616. {{citation}}: Check |url= value (help); Unknown parameter |sectionnum= ignored (help)
  57. ^ Bad Gateway RFC 2616. pp. 70. sec. 502 Bad Gateway. doi:10.17487/RFC2616. {{citation}}: Check |url= value (help); Unknown parameter |sectionnum= ignored (help)
  58. ^ Service Unavailable RFC 2616. p. 70. sec. 503 Service Unavailable. doi:10.17487/RFC2616. {{citation}}: Check |url= value (help); Unknown parameter |sectionnum= ignored (help)
  59. ^ Gateway Timeout RFC 2616. p. 71. sec. 504 Gateway Timeout. doi:10.17487/RFC2616. {{citation}}: Check |url= value (help); Unknown parameter |sectionnum= ignored (help)
  60. ^ HTTP Version Not Supported RFC 2616. p. 71. sec. 505 HTTP Version Not Supported. doi:10.17487/RFC2616. {{citation}}: Check |url= value (help); Unknown parameter |sectionnum= ignored (help)
  61. ^ Variant Also Negotiates RFC 2295. p. 25. sec. 506 Variant Also Negotiates. doi:10.17487/RFC2295. {{citation}}: Check |url= value (help); Unknown parameter |sectionnum= ignored (help)
  62. ^ Insufficient Storage RFC 4918. p. 79. sec. 507 Insufficient Storage. doi:10.17487/RFC4918. {{citation}}: Check |url= value (help); Unknown parameter |sectionnum= ignored (help)
  63. ^ Not Extended RFC 2774. p. 11. sec. 510 Not Extended. doi:10.17487/RFC2774. {{citation}}: Check |url= value (help); Unknown parameter |sectionnum= ignored (help)

References

Retrieved from "https://en.wikipedia.org/w/index.php?title=List_of_HTTP_status_codes&oldid=321774310"