Created
April 14, 2015 21:46
-
-
Save beenhere4hours/92f2cd3a7893ecaffe2e to your computer and use it in GitHub Desktop.
HTTP Response Codes
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Informational Responses | |
100 | |
Error Text: continue | |
Description: This interim response indicates that everything so far is OK and that the client should continue with the request or ignore it if it is already finished. | |
HTTP 1.0 only | |
101 | |
Error Text: switching protocol | |
Description: This code is sent in response to an Update: request header by the client, and indicates that the protocol the server is switching too. It was introduced to allow migration to an incompatible protocol version, and is not in common use. | |
HTTP 1.0 only | |
Successful responses | |
200 | |
Error Text: OK | |
Description: The request has succeeded. The meaning of a success varies depending on the HTTP method: | |
GET: The resource has been fetched and is transmitted in the message body. | |
HEAD: The entity headers are in the message body. | |
POST: The resource describing the result of the action is transmitted in the message body. | |
TRACE: The message body contains the request message as received by the server. The methods PUT, DELETE, and OPTIONS can never result in a 200 OK response. | |
HTTP/0.9 and later | |
201 | |
Error Text: Created | |
Description: The request has succeeded and a new resource has been created as a result of it. This is typically the response sent after a PUT request. | |
HTTP/0.9 and later | |
202 | |
Error Text: Accepted | |
Description: The request has been received but not yet acted upon. It is non-committal, meaning that there is no way in HTTP to later send an asynchronous response indicating the outcome of processing the request. It is intended for cases where another process or server handles the request, or for batch processing. | |
HTTP/0.9 and later | |
203 | |
Error Text: Non-Authoritative Information | |
Description: This response code means returned meta-information set is not exact set as available from the origin server, but collected from a local or a third party copy. Except this condition, 200 OK response should be preferred instead of this response. | |
HTTP/0.9 and 1.1 | |
204 | |
Error Text: No Content | |
Description: There is no content to send for this request, but the headers may be useful. The user-agent may update its cached headers for this resource with the new ones. | |
HTTP/0.9 and later | |
205 | |
Error Text: Reset Content | |
Description: This response code is sent after accomplishing request to tell user agent reset document view which sent this request. | |
HTTP/1.1 only | |
206 | |
Error Text: Partial Content | |
Description: This response code is used because of range header sent by the client to separate download into multiple streams. | |
HTTP/1.1 only | |
Redirection messages | |
300 | |
Error Text: Multiple Choice | |
Description: The request has more than one possible responses. User-agent or user should choice one of them. There is no standardized way to choice one of the responses. | |
HTTP/1.0 and later | |
301 | |
Error Text: Moved Permanently | |
Description: This response code means that URI of requested resource has been changed. Probably, new URI would be given in the response. | |
HTTP/0.9 and later | |
302 | |
Error Text: Found | |
Description: This response code means that URI of requested resource has been changed temporarily. New changes in the URI might be made in the future. Therefore, this same URI should be used by the client in future requests. | |
HTTP/0.9 and later | |
303 | |
Error Text: See Other | |
Description: Server sent this response to directing client to get requested resource to another URI with an GET request. | |
HTTP/0.9 and 1.1 | |
304 | |
Error Text: Not Modified | |
Description: This is used for caching purposes. It is telling to client that response has not been modified. So, client can continue to use same cached version of response. | |
HTTP/0.9 and later | |
305 | |
Error Text: Use Proxy | |
Description: This means requested response must be accessed by a proxy. This response code is not largely supported because security reasons. | |
HTTP/1.1 only | |
306 | |
Error Text: unused | |
Description: This response code is no longer used, it is just reserved currently. It was used in a previous version of the HTTP 1.1 specification. | |
HTTP/1.1 only | |
307 | |
Error Text: Temporary Redirect | |
Description: Server sent this response to directing client to get requested resource to another URI with same method that used prior request. This has the same semantic than the 302 Found HTTP response code, with the exception that the user agent <em>must not</em> change the HTTP method used: if a POST was used in the first request, a POST must be used in the second request. | |
HTTP/1.1 only | |
308 | |
Error Text: Permanent Redirect | |
Description: This means that the resource is now permanently located at another URI, specified by the <code>Location:</code> HTTP Response header. This has the same semantics as the 301 Moved Permanently HTTP response code, with the exception that the user agent <em>must not</em> change the HTTP method used: if a POST was used in the first request, a <code>POST</code> must be used in the second request. <div class="note"><strong>Note:</strong> This is an experimental response code whose <a class="external" href="http://greenbytes.de/tech/webdav/#draft-reschke-http-status-308" title="http://greenbytes.de/tech/webdav/#draft-reschke-http-status-308">specification</a> is currently in draft form.</div> | |
<a class="external" href="http://greenbytes.de/tech/webdav/draft-reschke-http-status-308-07.html" title="http://greenbytes.de/tech/webdav/draft-reschke-http-status-308-07.html">draft-reschke-http-status-308</a> | |
Client error responses | |
400 | |
Error Text: Bad Request | |
Description: This response means that server could not understand the request due to invalid syntax. | |
HTTP/0.9 and later | |
401 | |
Error Text: Unauthorized | |
Description: Authentication is needed to get requested response. This is similar to 403, but in this case, authentication is possible. | |
HTTP/0.9 and later | |
402 | |
Error Text: Payment Required | |
Description: This response code is reserved for future use. Initial aim for creating this code was using it for digital payment systems however this is not used currently. | |
HTTP/0.9 and 1.1 | |
403 | |
Error Text: Forbidden | |
Description: Client does not have access rights to the content so server is rejecting to give proper response. | |
HTTP/0.9 and later | |
404 | |
Error Text: Not Found | |
Description: Server can not find requested resource. This response code probably is most famous one due to its frequency to occur in web. | |
HTTP/0.9 and later | |
405 | |
Error Text: Method Not Allowed | |
Description: The request method is known by the server but has been disabled and cannot be used. The two mandatory methods, <code>GET</code> and <code>HEAD</code>, must never be disabled and should not return this error code. | |
HTTP/1.1 only | |
406 | |
Error Text: Not Acceptable | |
Description: This response is sent when the web server, after performing <a href="/en/HTTP/Content_negotiation#Server-driven_negotiation" title="https://developer.mozilla.org/en/HTTP/Content_negotiation#Server-driven_negotiation">server-driven content negotiation</a>, doesn't find any content following the criteria given by the user agent. | |
HTTP/1.1 only | |
407 | |
Error Text: Proxy Authentication Required | |
Description: This is similar to 401 but authentication is needed to be done by a proxy. | |
HTTP/1.1 only | |
408 | |
Error Text: Request Timeout | |
Description: This response is sent on an idle connection by some servers, even without any previous request by the client. It means that the server would like to shut down this unused connection. This response is used much more since some browsers, like Chrome or IE9, use <a class="external" href="http://www.belshe.com/2011/02/10/the-era-of-browser-preconnect/" title="http://www.belshe.com/2011/02/10/the-era-of-browser-preconnect/">HTTP preconnection mechanisms</a> to speed up surfing (see <a class="external" href="https://bugzilla.mozilla.org/show_bug.cgi?id=634278" title="">bug 634278</a>, which tracks the future implementation of such a mechanism in Firefox). Also note that some servers merely shut down the connection without sending this message. | |
HTTP/1.1 only | |
409 | |
Error Text: Conflict | |
Description: This response would be sent when a request conflict with current state of server. | |
HTTP/1.1 only | |
410 | |
Error Text: Gone | |
Description: This response would be sent when requested content has been deleted from server. | |
HTTP/1.1 only | |
411 | |
Error Text: Length Required | |
Description: Server rejected the request because the <code>Content-Length</code> header field is not defined and the server requires it. | |
HTTP/1.1 only | |
412 | |
Error Text: Precondition Failed | |
Description: The client has indicated preconditions in its headers which the server does not meet. | |
HTTP/1.1 only | |
413 | |
Error Text: Request Entity Too Large | |
Description: Request entity is larger than limits defined by server; the server might close the connection or return an <code>Retry-After</code> header field. | |
HTTP/1.1 only | |
414 | |
Error Text: Request-URI Too Long | |
Description: The URI requested by the client is too long for the server to handle. | |
HTTP/1.1 only | |
415 | |
Error Text: Unsupported Media Type | |
Description: The media format of the requested data is not supported by the server, so the server is rejecting the request. | |
HTTP/1.1 only | |
416 | |
Error Text: Requested Range Not Satisfiable | |
Description: The range specified by the <code>Range</code> header field in the request can't be fulfilled; it's possible that the range is outside the size of the target URI's data. | |
HTTP/1.1 only | |
417 | |
Error Text: Expectation Failed | |
Description: This response code means the expectation indicated by the <code>Expect</code> request header field can't be met by the server. | |
HTTP/1.1 only | |
Server error responses | |
500 | |
Error Text: Internal Server Error | |
Description: The server has encountered a situation it doesn't know how to handle. | |
HTTP/0.9 and later | |
501 | |
Error Text: Not Implemented | |
Description: The request method is not supported by the server and cannot be handled. The only methods that servers are required to support (and therefore that must not return this code) are <code>GET</code> and <code>HEAD</code>. | |
HTTP/0.9 and later | |
502 | |
Error Text: Bad Gateway | |
Description: This error response means that the server, while working as a gateway to get a response needed to handle the request, got an invalid response. | |
HTTP/0.9 and later | |
503 | |
Error Text: Service Unavailable | |
Description: The server is not ready to handle the request. Common causes are a server that is down for maintenance or that is overloaded. Note that together with this response, a user-friendly page explaining the problem should be sent. This responses should be used for temporary conditions and the <code>Retry-After:</code> HTTP header should, if possible, contain the estimated time before the recovery of the service. The webmaster must also take care about the caching-related headers that are sent along with this response, as these temporary condition responses should usually not be cached. | |
HTTP/0.9 and later | |
504 | |
Error Text: Gateway Timeout | |
Description: This error response is given when the server is acting as a gateway and cannot get a response in time. | |
HTTP/1.1 only | |
505 | |
Error Text: HTTP Version Not Supported | |
Description: The HTTP version used in the request is not supported by the server. | |
HTTP/1.1 only | |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment