Skip to content

Most Common HTTP Status Codes

HTTP status codes are grouped into five classes. The first digit of the status code defines the class of response.

1xx: Informational Responses

  • 100 Continue: The server has received the request headers and the client - hould proceed to send the request body.
  • 101 Switching Protocols: The requester has asked the server to switch - rotocols.
  • 102 Processing: The server has received and is processing the request, but - as not yet completed it.

  • 2xx: Successful Responses

  • 200 OK: The standard response for successful HTTP requests.

  • 201 Created: The request has been fulfilled, resulting in the creation of a - ew resource.
  • 202 Accepted: The request has been accepted for processing, but processing is - ot yet complete.

  • 204 No Content: The server successfully processed the request but is not - eturning any content.

  • 3xx: Redirection Messages

  • 301 Moved Permanently: This and all future requests should be directed to the - iven URI.

  • 302 Found (or "Moved Temporarily"): The resource is temporarily located at a - ifferent URI.

  • 304 Not Modified: Indicates that the resource has not been modified since the - ersion specified by the request headers.

  • 4xx: Client Error Responses

  • 400 Bad Request: The server cannot process the request due to an apparent - lient error (e.g., malformed syntax).

  • 401 Unauthorized: Authentication is required and has failed or not yet been - rovided.
  • 403 Forbidden: The request was valid, but the server is refusing action. The - ser might not have the necessary permissions.
  • 404 Not Found: The requested resource could not be found on the server.
  • 405 Method Not Allowed: The request method (e.g., GET, POST) is not supported - or the requested resource.
  • 408 Request Timeout: The server timed out waiting for the request from the - lient.
  • 409 Conflict: The request could not be processed because of a conflict in the - urrent state of the resource.
  • 429 Too Many Requests: The user has sent too many requests in a given amount - f time ("rate limiting").

  • 5xx: Server Error Responses

  • 500 Internal Server Error: A generic error message when the server encounters - n unexpected condition.
  • 501 Not Implemented: The server does not support the functionality required to - ulfill the request.
  • 502 Bad Gateway: The server was acting as a gateway or proxy and received an - nvalid response from the upstream server.
  • 503 Service Unavailable: The server is currently unavailable (e.g., down for - aintenance or overloaded).
  • 504 Gateway Timeout: The server was acting as a gateway or proxy and did not - eceive a timely response from the upstream server.