HTTP Status Codes

HTTP status codes are three-digit numbers returned by servers to indicate the result of a client's request. They are grouped into five classes: informational (1xx), success (2xx), redirection (3xx), client error (4xx), and server error (5xx).

1xx — Informational

Code Name Description
100 Continue The server has received the request headers, and the client should proceed to send the request body.
101 Switching Protocols The requester has asked the server to switch protocols and the server has agreed to do so.
102 Processing The server has received and is processing the request, but no response is available yet.
103 Early Hints Used to return some response headers before final HTTP message.

2xx — Success

Code Name Description
200 OK The request has succeeded. The meaning of the success depends on the HTTP method.
201 Created The request has been fulfilled and resulted in a new resource being created.
202 Accepted The request has been accepted for processing, but the processing has not been completed.
203 Non-Authoritative Information The server successfully processed the request but is returning information from another source.
204 No Content The server successfully processed the request and is not returning any content.
205 Reset Content The server successfully processed the request, the requester should reset the document view.
206 Partial Content The server is delivering only part of the resource due to a range header sent by the client.
207 Multi-Status The message body contains multiple status codes for multiple independent operations.

3xx — Redirection

Code Name Description
301 Moved Permanently The requested resource has been assigned a new permanent URI.
302 Found The requested resource resides temporarily under a different URI.
303 See Other The response to the request can be found under another URI using GET.
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.
308 Permanent Redirect The request and all future requests should be repeated using another URI.

4xx — Client Error

Code Name Description
400 Bad Request The server cannot process the request due to something perceived to be a client error.
401 Unauthorized Authentication is required and has failed or has not been provided.
403 Forbidden The server understood the request but refuses to authorize it.
404 Not Found The requested resource could not be found on the server.
405 Method Not Allowed The request method is not supported for the requested resource.
406 Not Acceptable The requested resource can only generate content not acceptable according to the Accept headers.
408 Request Timeout The server timed out waiting for the request.
409 Conflict The request could not be processed because of conflict in the current state of the resource.
410 Gone The requested resource is no longer available and will not be available again.
413 Payload Too Large The request is larger than the server is willing or able to process.
414 URI Too Long The URI provided was too long for the server to process.
415 Unsupported Media Type The request entity has a media type which the server does not support.
418 I'm a Teapot The server refuses to brew coffee because it is a teapot. (RFC 2324)
422 Unprocessable Entity The request was well-formed but was unable to be followed due to semantic errors.
429 Too Many Requests The user has sent too many requests in a given amount of time (rate limiting).
451 Unavailable For Legal Reasons The resource is unavailable due to legal demands.

5xx — Server Error

Code Name Description
500 Internal Server Error A generic error message when an unexpected condition was encountered by the server.
501 Not Implemented The server does not support the functionality required to fulfill the request.
502 Bad Gateway The server received an invalid response from the upstream server.
503 Service Unavailable The server is currently unable to handle the request due to maintenance or overloading.
504 Gateway Timeout The server did not receive a timely response from the upstream server.
505 HTTP Version Not Supported The server does not support the HTTP protocol version used in the request.
507 Insufficient Storage The server is unable to store the representation needed to complete the request.
511 Network Authentication Required The client needs to authenticate to gain network access (e.g., captive portal).