Common HTTP Status Codes

Notes: 1xx status codes indicate provisional responses, such as 100 Continue or 101 Switching Protocols.

100 Continue

The server has received the initial part of the request and is waiting for the client to send the remainder.

101 Switching Protocols

The client has asked the server to change protocols and the server has agreed to do so.

102 Processing

The server has received and is processing the request, but that it does not have a final response yet.

Notes: 2xx status codes indicate that the client's request was successfully received, understood, and accepted. Examples include 200 OK or 201 Created.

200 OK

The request was successful.

201 Created

The request has been fulfilled, and a new resource has been created.

202 Accepted

The request has been accepted for processing, but the processing has not been completed.

204 No Content

The server successfully processed the request but isn't returning any content.

Notes: 3xx status codes indicate that further action needs to be taken to complete the request. Examples include 301 Moved Permanently or 302 Found.

300 Multiple Choices

Indicates that there exist multiple options for the resource at the server that the client may choose from.

301 Moved Permanently

The requested resource has been permanently moved to a new location.

302 Found (Previously "Moved Temporarily")

The requested resource has been temporarily moved to a different URI.

304 Not Modified

The client's cached copy is still valid and the server does not need to send a new copy.

Notes: 4xx status codes indicate that there was an error on the client's end. Examples include 400 Bad Request or 404 Not Found.

400 Bad Request

The server could not understand the request due to invalid syntax.

401 Unauthorized

Authentication is required and has failed or has not yet been provided.

403 Forbidden

The client does not have permission to access the requested resource.

404 Not Found

The requested resource could not be found on the server.

407 Proxy Authentication Required

The client must first authenticate itself with the proxy to make a successful request with to the server.

408 Request Timeout

The server timed out waiting for the request from the client.

Notes: 5xx status codes indicate that there was an error on the server's end. Examples include 500 Internal Server Error or 503 Service Unavailable.

500 Internal Server Error

A generic error message indicating that something went wrong on the server's end.

501 Not Implemented

The server does not support the functionality required to fulfill the request.

502 Bad Gatewa

The server received an invalid response from an upstream server.

503 Service Unavailable

The server is currently unable to handle the request due to temporary overload or maintenance of the server.

504 Gateway Timeout

The server, while acting as a gateway or proxy, did not receive a timely response from the upstream server.