HTTP Status Code Explainer
A quick reference for HTTP status codes.
1xx Informational
100 Continue
The server has received the request headers and the client should proceed to send the request body.
101 Switching Protocols
The server is switching protocols to one requested by the client.
102 Processing
The server has received and is processing the request, but no response is available yet.
2xx Success
200 OK
The request has succeeded.
201 Created
The request has been fulfilled and has resulted in one or more new resources being 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 and is not returning any content.
3xx Redirection
301 Moved Permanently
This and all future requests should be directed to the given URI.
302 Found
The resource was found but at a different URI. Clients should continue to use the original URI.
304 Not Modified
The resource has not been modified since the version specified by the request headers.
307 Temporary Redirect
The request should be repeated with another URI, but future requests should still use the original URI.
4xx Client Error
400 Bad Request
The server cannot process the request due to a client error (e.g., malformed request syntax).
401 Unauthorized
The client must authenticate itself to get the requested response.
403 Forbidden
The client does not have access rights to the content.
404 Not Found
The server cannot find the requested resource.
405 Method Not Allowed
The request method is known by the server but is not supported by the target resource.
429 Too Many Requests
The user has sent too many requests in a given amount of time ("rate limiting").
5xx Server Error
500 Internal Server Error
The server has encountered a situation it doesn't know how to handle.
501 Not Implemented
The request method is not supported by the server and cannot be handled.
502 Bad Gateway
The server, while acting as a gateway or proxy, received an invalid response from the upstream server.
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.
504 Gateway Timeout
The server is acting as a gateway and cannot get a response in time.