Overview#

The HTTP protocol provides a rich set of status Result Codes to represent different request processing outcomes and are in the IANA Registry Hypertext Transfer Protocol (HTTP) Status Code Registry
  • 1xx: Informational - Request received, continuing process
  • 2xx: Success - The action was successfully received, understood, and accepted
  • 3xx: Redirection - Further action must be taken in order to complete the request
  • 4xx: Client Error - The request contains bad syntax or cannot be fulfilled
  • 5xx: Server Error - The server failed to fulfill an apparently valid request

codeTypeStatus textDescriptionHTTP version
100InformationalContinueThis 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.1 only
101InformationalSwitching ProtocolThis code is sent in response to an Upgrade: 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.1 only
102InformationalProcessinginterim response used to inform the client that the server has accepted the complete request, but has not yet completed it.RFC 2518
200SuccessfulOKThe 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
HTTP/0.9 and later
201SuccessfulCreatedThe 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
202SuccessfulAcceptedThe 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
203SuccessfulNon-Authoritative InformationThis 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
204SuccessfulNo ContentThere 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
205SuccessfulReset ContentThis response code is sent after accomplishing request to tell user agent reset document view which sent this request.HTTP/1.1 only
206SuccessfulPartial ContentThis response code is used because of range header sent by the client to separate download into multiple streams.HTTP/1.1 only
207SuccessfulMulti-StatusThis response code is is used as the overall response status code, the recipient needs to consult the contents of the multistatus response body for further information about the success or failure of the method execution.RFC 4918
208SuccessfulAlready Reportedstatus code can be used inside a DAV: propstat response element to avoid enumerating the internal members of multiple bindings to the same collection repeatedly. Can only occur for "Depth: infinity" requests when the where multiple collection bindings cause a bind loopRFC5842
209-225UnassignedThis response code is no longer used, it is just reserved currently.
226SuccessfulIM UsedThe server has fulfilled a GET request for the resource, and the response is a representation of the result of one or more instance-manipulations applied to the current instanceRFC 3229
227-299UnassignedThis response code is no longer used, it is just reserved currently.
300RedirectionMultiple ChoiceThe request has more than one possible responses. User-agent or user should choose one of them. There is no standardized way to choose one of the responses.HTTP/1.0 and later
301RedirectionMoved PermanentlyThis 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
302RedirectionFoundThis 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
303RedirectionSee OtherServer sent this response to directing client to get requested resource to another URI with an GET request.HTTP/0.9 and 1.1
304RedirectionNot ModifiedThis 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
305RedirectionUse ProxyThis means requested response must be accessed by a proxy. This response code is not largely supported because security reasons.HTTP/1.1 only
306RedirectionunusedThis 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
307RedirectionTemporary RedirectServer 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 must not 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
308RedirectionPermanent RedirectThis means that the resource is now permanently located at another URI, specified by the Location: HTTP Response header. This has the same semantics as the 301 Moved Permanently HTTP response code, with the exception that the user agent must not change the HTTP method used: if a POST was used in the first request, a POST must be used in the second request.RFC 7538
400errorBad RequestThis response means that server could not understand the request due to invalid syntax.HTTP/0.9 and later
401errorUnauthorizedAuthentication is needed to get requested response. This is similar to 403, but in this case, authentication is possible.HTTP/0.9 and later
402errorPayment RequiredThis 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
403errorForbiddenClient does not have access rights to the content so server is rejecting to give proper response.HTTP/0.9 and later
404errorNot FoundServer 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
405errorMethod Not AllowedThe request method is known by the server but has been disabled and cannot be used. The two mandatory methods, GET and HEAD, must never be disabled and should not return this error code.HTTP/1.1 only
406errorNot AcceptableThis response is sent when the web server, after performing server-driven content negotiation, doesn't find any content following the criteria given by the user agent.HTTP/1.1 only
407errorProxy Authentication RequiredThis is similar to 401 but authentication is needed to be done by a proxy.HTTP/1.1 only
408errorRequest TimeoutThis 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 HTTP preconnection mechanisms to speed up surfing (see bug 881804, 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
409errorConflictThis response would be sent when a request conflict with current state of server.HTTP/1.1 only
410errorGoneThis response would be sent when requested content has been deleted from server.HTTP/1.1 only
411errorLength RequiredServer rejected the request because the Content-Length header field is not defined and the server requires it.HTTP/1.1 only
412errorPrecondition FailedThe client has indicated preconditions in its headers which the server does not meet.HTTP/1.1 only
413errorPayload Too LargeRequest entity is larger than limits defined by server; the server might close the connection or return an Retry-After header field.HTTP/1.1 only
414errorURI Too LongThe URI requested by the client is longer than the server is willing to interpret.HTTP/1.1 only
415errorUnsupported Media TypeThe media format of the requested data is not supported by the server, so the server is rejecting the request.HTTP/1.1 only
416errorRequested Range Not SatisfiableThe range specified by the Range 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
417errorExpectation FailedThis response code means the expectation indicated by the Expect request header field can't be met by the server.HTTP/1.1 only
418errorI'm a teapotAny attempt to brew coffee with a teapot should result in the error code "418 I'm a teapot". The resulting entity body MAY be short and stout.HTCPCP/1.0
418-420Unassigned
421errorMisdirected RequestThe request was directed at a server that is not able to produce a response. This can be sent by a server that is not configured to produce responses for the combination of scheme and authority that are included in the request URI.HTTP/2.0
422error Unprocessable EntityThe server understands the content type of the request entity and the syntax of the request entity is correct but was unable to process the contained instructions.RFC 4918
423errorLockedMeans the source or destination resource of a method is locked. This response SHOULD contain an appropriate precondition or postcondition code, such as 'lock-token-submitted' or 'no-conflicting-lock'RFC 4918
424errorFailed DependencyThe method could not be performed on the resource because the requested action depended on another action and that action failedRFC 4918
426errorUpgrade RequiredThe server refuses to perform the request using the current protocol but might be willing to do so after the client upgrades to a different protocol. The server MUST send an Upgrade header field in a 426 response to indicate the required protocol(s) (Section 6.7 of RFC7230).HTTP/1.1 and newer
428errorPrecondition RequiredThe 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."HTTP/1.1 and newer
429errorToo Many RequestsThe user has sent too many requests in a given amount of time ("rate limiting").HTTP/1.1 and newer
431errorRequest Header Fields Too LargeThe server is unwilling to process the request because its header fields are too large. The request MAY be resubmitted after reducing the size of the request header fields.HTTP/1.1 and newer
432-450Unassigned
451errorUnavailable For Legal ReasonsThis status code indicates that the server is denying access to the resource as a consequence of a legal demandRFC-ietf-httpbis-legally-restricted-status-04
452-499Unassigned
500ServerInternal Server ErrorThe server has encountered a situation it doesn't know how to handle.HTTP/0.9 and later
501ServerNot ImplementedThe 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 GET and HEAD.HTTP/0.9 and later
502ServerBad GatewayThis 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
503ServerService UnavailableThe 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 Retry-After: 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
504ServerGateway TimeoutThis error response is given when the server is acting as a gateway and cannot get a response in time.HTTP/1.1 only
505ServerHTTP Version Not SupportedThe HTTP version used in the request is not supported by the server.HTTP/1.1 only
506ServerVariant Also NegotiatesThe server has an internal configuration error: transparent content negotiation for the request results in a circular reference.HTTP/1.1
507ServerInsufficient Storagethe method could not be performed on the resource because the server is unable to store the representation needed to successfully complete the request. This condition is considered to be temporaryRFC 4918
508ServerLoop DetectedThe server terminated an operation because it encountered an infinite loop while processing a request with "Depth: infinity". This status indicates that the entire operation failed.RFC 5842
509Unassigned
510ServerNot ExtendedThe policy for accessing the resource has not been met in the request.RFC 2774
511ServerNetwork Authentication RequiredThe 511 status code indicates that the client needs to authenticate to gain network access.HTTP/1.1
512-599Unassigned

More Information#

There might be more information for this subject on one of the following:

Add new attachment

Only authorized users are allowed to upload new attachments.
« This page (revision-18) was last changed on 22-May-2017 12:01 by jim