Skip to content

HTTP Status Codes

1xx Informational Response

  • 100 Continue - The server has received the request headers and the client should proceed to send the request body
  • 101 Switching Protocols - the requester has asked the server to switch protocols and the server has agreed to do so
  • 102 Processing - This code indicates that the server has received and is processing the request, but no response is available yet.
  • 103 Early Hints - Used to return some response headers before the final HTTP message.

2xx Success

  • 200 - OK. Standard response for successful HTTP requests.
  • 201 - Created. The request has been fulfilled, resulting in the creation of a new resource.
  • 202 - Accepted. The Request has been accepted for processing.
  • 203 - Non-Authoritative Information. The server is a transforming proxy that received a 200 OK from the origin, but is returning a modified version of the origin's response.
  • 204 - No Content. The server has processed successfully the request, and it is not returning any content.
  • 205 - Reset Content. The server has processed successfully the request, asks that the requester resets its document view, and it is not returning any content.
  • 206 - Partial Content. The server is delivering only a part of the resource due to a range header sent by the client. The range header is used by HTTP clients to enable resuming of interrupted downloads, or split a download into multiple simultaneous streams.
  • 207 - Multi Status. The body message that follows is by default an XML message and can contain a number of separate response codes, depending on how many sub-requests were made.
  • 208 - Already Reported. The members of a DAV binding have already been enumerated in a preceding part of the (multistatus) response, and are not being included again.
  • 226 - IM Used. The server has fulfilled a request for the resource, and the response is a representation of the result of one or more instance-manipulations applied to the current instance.

3xx Redirection

  • 300 - Multiple choices. Indicates multiple options for the resource from which the client may choose. For example, this code could be used to present multiple video format options, to list files with different filename extensions, or to suggest word-sense disambiguation.
  • 301 - Moved Permanently. This and all future requests should be directed to the given URI.
  • 302 - Found (Previously "Moved Temporarily"). Tells the client to look at another URL. 302 has been replaced by 303 and 307.
  • 303 - See Other. The response to the request can be found under another URI, using the GET method.
  • 304 - Not Modified. Indicates that the request has not been modified since the specified version by the request headers.
  • 305 - Use Proxy. The requested resource is available only through a proxy, the address is provided in the response. For security reasons many HTTP clients (Mozilla Firefox and Internet Explorer) do not obey this status code.
  • 306 - Switch Proxy. No longer used. Originally meant "Subsequent requests should use the specified proxy".
  • 307 - Temporary Redirect. In this case, the request should be repeated with another URI; however, future requests should still use the original URI. In contrast to how 302 was historically implemented, the request method is not allowed to be changed when reissuing the original request. For example, a POST request should be repeated using another POST request.
  • 308 - Permanent Redirect. The request and all future requests should be repeated using another URI. 307 and 308 parallel the behaviors of 302 and 301, but do not allow the HTTP method to change. So, for example, submitting a form to a permanently redirected resource may continue smoothly.

4xx Client errors

  • 400 - Bad Request. The server cannot or will not process the request due to an apparent client error (e.g., malformed request syntax, size too large, invalid request message framing, or deceptive request routing).
  • 401 - Unauthorized. Similar to 403 Forbidden, but specifically for use when authentication is required and has failed or has not yet been provided. The response must include a WWW-Authenticate header field containing a challenge applicable to the requested resource.
  • 402 - Payment Required. Reserved for future use.
  • 403 - Forbidden. The request contained valid data and was understood by the server, but the server is refusing action.
  • 404 - Not Found. The requested resource could not be found but may be available in the future.
  • 405 - Method Not Allowed. A request method is not supported for the requested resource.
  • 406 - Not Acceptable. The resource identified by this request is only capable of generating responses with characteristics not acceptable according to the request "accept" headers
  • 407 - Proxy Authentication Required. The client must first authenticate itself with the proxy.
  • 408 - Request Timeout. The server timed out waiting for the request.
  • 409 - Conflict. Indicates that the request could not be processed because of conflict in the current state of the resource, such as an edit conflict between multiple simultaneous updates.
  • 410 - Gone. Indicates that the resource requested is no longer available and will not be available again.
  • 411 - Length Required. The request did not specify the length of its content, which is required by the requested resource.
  • 412 - Precondition Failed. The server does not meet one of the preconditions that the requester put on the request header fields.
  • 413 - Payload Too Large. The request is larger than the server is willing or able to process.
  • 414 - URI Too Long. The URI provided was too long for the server to process.
  • 415 - Unsupported Media Type. The request entity has a media type which the server or resource does not support.
  • 416 - Range Not Satisfiable. The client has asked for a portion of the file, but the server cannot supply that portion.
  • 417 - Expectation Failed. The server cannot meet the requirements of the Expect request-header field.
  • 421 - Misdirected Request. The request was directed at a server that is not able to produce a response.
  • 422 - Non-processable Entity. The request was well-formed but was unable to be followed due to semantic errors.
  • 423 - Locked. The resource that is being accessed is locked.
  • 424 - Failed Dependency. The request has failed because it depended on another failed request.
  • 425 - Too Early. Indicates that the server is unwilling to risk processing a request that might be replayed.
  • 426 - Upgrade Required. The client should switch to a different protocol.
  • 428 - Precondition Required. The origin server requires the request to be conditional.
  • 429 - Too Many Requests. The user has sent too many requests in a given amount of time.
  • 431 - Request Header Fields Too Large. The server is unwilling to process the request because either an individual header field, or all the header fields, are too large.
  • 451 - Unavailable for Leagal Reasons. A server operator has received a legal demand to deny access to a resource or to a set of resources that includes the requested resource.

5xx Server Errors

  • 500 - Internal Server Error. A generic error message, given when an unexpected condition was encountered and no more specific message is suitable.
  • 501 - Not Implemented. The server either does not recognize the request method, or it lacks the ability to fulfill it.
  • 502 - Bad Gateway. The server was acting as a gateway or proxy and received an invalid response from the upstream server.
  • 503 - Service Unavailable. The server cannot handle the request (because it is overloaded or down for maintenance). Generally, this is a temporary state.
  • 504 - Gateway Timeout. The server was acting as a gateway or proxy and did not receive a timely response from the upstream server.
  • 505 - HTTP Version Not Supported. The server does not support the HTTP protocol version used in the request.
  • 506 - Variant Also Negotiates. Transparent content negotiation for the request results in a circular reference.
  • 507 - Insufficient Storage. The server is unable to store the representation needed to complete the request.
  • 508 - Loop Detected. The server has detected an infinite loop while processing the request.
  • 510 - Not Extended. Further extensions to the request are required for the server to fulfill it.
  • 511 - Network Authentication Required. The client needs to authenticate to gain network access.