Skip to main content

HTTP Status Codes

Common Codes

Status CodeCategoryDefinition
100InformationalContinue: The server has received the request headers, and the client should proceed to send the request body.
101InformationalSwitching Protocols: The requester has asked the server to switch protocols and the server has agreed to do so.
200SuccessfulOK: The request has succeeded.
201SuccessfulCreated: The request has been fulfilled, and a new resource is created.
202SuccessfulAccepted: The request has been accepted for processing, but the processing has not been completed.
204SuccessfulNo Content: The server successfully processed the request, but is not returning any content.
301RedirectionMoved Permanently: The requested resource has been assigned a new permanent URI and any future references to this resource should use one of the returned URIs.
302RedirectionFound: The requested resource resides temporarily under a different URI.
304RedirectionNot Modified: There was no new data to return.
400Client ErrorBad Request: The request cannot be fulfilled due to bad syntax.
401Client ErrorUnauthorized: Similar to 403 Forbidden, but specifically for use when authentication is required and has failed or has not yet been provided.
403Client ErrorForbidden: The request was a valid request, but the server is refusing to respond to it.
404Client ErrorNot Found: The requested resource could not be found but may be available again in the future.
500Server ErrorInternal Server Error: A generic error message, given when an unexpected condition was encountered and no more specific message is suitable.
501Server ErrorNot Implemented: The server either does not recognize the request method, or it lacks the ability to fulfill the request.
503Server ErrorService Unavailable: The server is currently unavailable (because it is overloaded or down for maintenance). Generally, this is a temporary state.

Extended Codes

Status CodeCategoryDefinition
405Client ErrorMethod Not Allowed: The method specified in the Request-Line is not allowed for the resource identified by the request.
406Client ErrorNot Acceptable: The server cannot produce a response matching the list of acceptable values defined in the request's proactive content negotiation headers.
407Client ErrorProxy Authentication Required: Similar to 401 Unauthorized, but it indicates that the client must first authenticate itself with the proxy.
408Client ErrorRequest Timeout: The server timed out waiting for the request.
409Client ErrorConflict: The request could not be completed due to a conflict with the current state of the resource.
410Client ErrorGone: The requested resource is no longer available at the server and no forwarding address is known.
411Client ErrorLength Required: The request did not specify the length of its content, which is required by the requested resource.
412Client ErrorPrecondition Failed: The server does not meet one of the preconditions that the requester put on the request.
413Client ErrorPayload Too Large: The request is larger than the server is willing or able to process.
414Client ErrorURI Too Long: The URI provided was too long for the server to process.
415Client ErrorUnsupported Media Type: The request entity has a media type which the server or resource does not support.
416Client ErrorRange Not Satisfiable: The client has asked for a portion of the file, but the server cannot supply that portion.
417Client ErrorExpectation Failed: The server cannot meet the requirements of the Expect request-header field.
422Client ErrorUnprocessable Entity: The request was well-formed but was unable to be followed due to semantic errors.
429Client ErrorToo Many Requests: The user has sent too many requests in a given amount of time ("rate limiting").
502Server ErrorBad Gateway: The server was acting as a gateway or proxy and received an invalid response from the upstream server.
504Server ErrorGateway Timeout: The server was acting as a gateway or proxy and did not receive a timely response from the upstream server.
505Server ErrorHTTP Version Not Supported: The server does not support the HTTP protocol version that was used in the request.
507Server ErrorInsufficient Storage: The server is unable to store the representation needed to complete the request.
508Server ErrorLoop Detected: The server detected an infinite loop while processing the request (used in WebDAV).