HTTP Status Codes

Categories

  • 1xx: Information responses

  • 2xx: Successful responses

  • 3xx: Redirection messages

  • 4xx: Client error responses

  • 5xx: Server error responses

Common Status Codes

  • 200 OK

    • The request succeeded. The result meaning of "success" depends on the HTTP method:

      • GET: The resource has been fetched and transmitted in the message body.

      • HEAD: The representation headers are included in the response without any message body.

      • PUT or 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.

  • 301 Moved Permanently

    • The URL of the requested resource has been changed permanently. The new URL is given in the response.

  • 302 Found

    • This response code means that the URI of requested resource has been changed temporarily. Further changes in the URI might be made in the future. Therefore, this same URI should be used by the client in future requests.

  • 304 Not Modified

    • This is used for caching purposes. It tells the client that the response has not been modified, so the client can continue to use the same cached version of the response.

  • 400 Bad Request

    • The server cannot or will not process the request due to something that is perceived to be a client error (e.g., malformed request syntax, invalid request message framing, or deceptive request routing).

  • 401 Unauthorized

    • Although the HTTP standard specifies "unauthorized", semantically this response means "unauthenticated". That is, the client must authenticate itself to get the requested response.

  • 403 Forbidden

    • The client does not have access rights to the content; that is, it is unauthorized, so the server is refusing to give the requested resource. Unlike 401 Unauthorized, the client's identity is known to the server.

  • 404 Not Found

    • The server can not find the requested resource. In the browser, this means the URL is not recognized. In an API, this can also mean that the endpoint is valid but the resource itself does not exist. Servers may also send this response instead of 403 Forbidden to hide the existence of a resource from an unauthorized client. This response code is probably the most well known due to its frequent occurrence on the web.

  • 500 Internal Server Error

    • The server has encountered a situation it does not know how to handle.

  • 503 Service Unavailable

    • The 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 response 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.

Reference

PreviousHTTPNextHTTP Headers

Last updated