HTTP Status Codes

1xx Informational Response

  • 100: Continue: Waiting for the client to emit the body of the request.
  • 101: Switching Protocols: The server has agreed to change protocol.
  • 102: Processing: The server is processing the request, but no response is available yet.
  • 103: Early Hints: The server returns some response headers before 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, but the processing has not been completed.
  • 203: Non-Authoritative Information: The request is successful but the content has been modified.
  • 204: No Content: The server successfully processed the request and is not returning any content.
  • 205: Reset Content: The server indicates to reinitialize the document view.
  • 206: Partial Content: The server is delivering only part of the resource.
  • 207: Multi-Status: The message body that follows is an XML message with multiple response codes.
  • 208: Already Reported: Members of a DAV binding have already been enumerated.
  • 226: IM Used: The server has fulfilled a request for the resource.

3xx Redirection

  • 300: Multiple Choices: Indicates multiple options for the resource.
  • 301: Moved Permanently: Future requests should be directed to the given URI.
  • 302: Found: Redirect to another URL.
  • 303: See Other: The response can be found under another URI.
  • 304: Not Modified: The resource has not been modified.
  • 305: Use Proxy: The resource is only available through a proxy.
  • 306: Switch Proxy: No longer used.
  • 307: Temporary Redirect: The request should be repeated with another URI.
  • 308: Permanent Redirect: Future requests should be repeated using another URI.

4xx Client Error

  • 400: Bad Request: The server cannot or will not process the request due to a client error.
  • 401: Unauthorized: Authentication is required and has failed.
  • 402: Payment Required: Reserved for future use.
  • 403: Forbidden: The request was valid, but the server is refusing action.
  • 404: Not Found: The requested resource could not be found.
  • 405: Method Not Allowed: A request method is not supported for the requested resource.
  • 406: Not Acceptable: The requested resource is not acceptable.
  • 407: Proxy Authentication Required: The client must authenticate with the proxy.
  • 408: Request Timeout: The server timed out waiting for the request.
  • 409: Conflict: The request could not be processed due to a conflict.
  • 410: Gone: The resource is no longer available.
  • 411: Length Required: The request did not specify the length of its content.
  • 412: Precondition Failed: The server does not meet the preconditions.
  • 413: Payload Too Large: The request is larger than the server can process.
  • 414: URI Too Long: The URI provided was too long.
  • 415: Unsupported Media Type: The request entity has a media type which is not supported.
  • 416: Range Not Satisfiable: The client has asked for a portion of the file.
  • 417: Expectation Failed: The server cannot meet the requirements of the Expect request-header.
  • 418: I'm a teapot: The server refuses the attempt to brew coffee.
  • 421: Misdirected Request: The request was directed at a server that cannot produce a response.
  • 422: Unprocessable Entity: The request was well-formed but unable to be followed.
  • 423: Locked: The resource that is being accessed is locked.
  • 424: Failed Dependency: The request failed due to failure of a previous request.
  • 425: Too Early: 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.
  • 431: Request Header Fields Too Large: The server is unwilling to process the request.
  • 451: Unavailable For Legal Reasons: A legal demand has been received to deny access.

5xx Server Error

  • 500: Internal Server Error: A generic error message.
  • 501: Not Implemented: The server does not recognize the request method.
  • 502: Bad Gateway: The server received an invalid response from the upstream server.
  • 503: Service Unavailable: The server is currently unavailable.
  • 504: Gateway Timeout: The server did not receive a timely response.
  • 505: HTTP Version Not Supported: The server does not support the HTTP protocol version.
  • 506: Variant Also Negotiates: Transparent content negotiation resulted in a circular reference.
  • 507: Insufficient Storage: The server is unable to store the representation.
  • 508: Loop Detected: The server detected an infinite loop.
  • 510: Not Extended: Further extensions to the request are required.
  • 511: Network Authentication Required: A network authentication is required.