HTTP Status Reference
61 codes
1xx
Informational
4 codes
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 to the protocol the client requested via an Upgrade header.
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 the final HTTP message.
2xx
Success
10 codes
200
OK
The request succeeded. The meaning of success depends on the HTTP method used.
201
Created
The request succeeded and a new resource was created as a result.
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 modified information from a third-party source.
204
No Content
The server successfully processed the request but is not returning any content.
205
Reset Content
The server successfully processed the request and asks the client to 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
A WebDAV response that conveys information about multiple resources where multiple status codes might be appropriate.
208
Already Reported
Used in a WebDAV DAV:propstat response to avoid repeatedly enumerating the internal members of multiple bindings to the same collection.
226
IM Used
The server has fulfilled a GET request and the response is a representation of the result of one or more instance-manipulations applied to the current instance.
3xx
Redirection
7 codes
300
Multiple Choices
The request has more than one possible response. The client should choose one of them.
301
Moved Permanently
The URL of the requested resource has been changed permanently. The new URL is given in the response.
302
Found
The URI of the requested resource has been changed temporarily. The client should continue using the original URI.
303
See Other
The server sent this response to direct the client to get the requested resource at another URI with a GET request.
304
Not Modified
Indicates that the resource has not been modified since the last request. The client can use its cached copy.
307
Temporary Redirect
The server sends this to direct the client to the requested resource at another URI with the same method.
308
Permanent Redirect
The resource has permanently moved and the client should use the new URI with the same HTTP method.
4xx
Client Error
29 codes
400
Bad Request
The server cannot process the request due to something perceived to be a client error (malformed syntax, invalid framing, etc.).
401
Unauthorized
The client must authenticate itself to get the requested response. Semantically means 'unauthenticated'.
402
Payment Required
Reserved for future use. Originally intended for digital payment systems.
403
Forbidden
The client does not have access rights to the content. Unlike 401, the client's identity is known to the server.
404
Not Found
The server cannot find the requested resource. The URL is not recognized or the resource doesn't exist.
405
Method Not Allowed
The request method is known by the server but not supported by the target resource.
406
Not Acceptable
The server cannot produce a response matching the list of acceptable values in the request's Accept headers.
407
Proxy Authentication Required
Similar to 401 but authentication is needed with a proxy between the client and server.
408
Request Timeout
The server timed out waiting for the request. The client did not produce a request within the expected time.
409
Conflict
The request conflicts with the current state of the server.
410
Gone
The requested content has been permanently deleted from the server with no forwarding address.
411
Length Required
The server rejected the request because the Content-Length header is not defined and the server requires it.
412
Precondition Failed
The client has indicated preconditions in its headers which the server does not meet.
413
Payload Too Large
The request entity is larger than limits defined by the server.
414
URI Too Long
The URI requested by the client is longer than the server is willing to interpret.
415
Unsupported Media Type
The media format of the requested data is not supported by the server.
416
Range Not Satisfiable
The range specified by the Range header in the request cannot be fulfilled.
417
Expectation Failed
The expectation given in the Expect header could not be met by the server.
418
I'm a Teapot
The server refuses the attempt to brew coffee with a teapot. An April Fools' joke from RFC 2324.
421
Misdirected Request
The request was directed at a server that is not able to produce a response.
422
Unprocessable Entity
The request was well-formed but the server was unable to process the contained instructions due to semantic errors.
423
Locked
The resource that is being accessed is locked.
424
Failed Dependency
The request failed because it depended on another request that failed.
425
Too Early
The server is unwilling to risk processing a request that might be replayed.
426
Upgrade Required
The server refuses to perform the request using the current protocol but might after the client upgrades.
428
Precondition Required
The origin server requires the request to be conditional to prevent lost updates.
429
Too Many Requests
The user has sent too many requests in a given amount of time (rate limiting).
431
Request Header Fields Too Large
The server is unwilling to process the request because its header fields are too large.
451
Unavailable For Legal Reasons
The resource is unavailable due to legal demands (censorship, court order, etc.).
5xx
Server Error
11 codes
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 include maintenance or overloading.
504
Gateway Timeout
The server, acting as a gateway, did not receive a timely response from the upstream server.
505
HTTP Version Not Supported
The HTTP version used in the request is not supported by the server.
506
Variant Also Negotiates
The server has an internal configuration error: transparent content negotiation results in a circular reference.
507
Insufficient Storage
The server is unable to store the representation needed to complete the request.
508
Loop Detected
The server detected an infinite loop while processing the request.
510
Not Extended
Further extensions to the request are required for the server to fulfill it.
511
Network Authentication Required
The client needs to authenticate to gain network access, typically from a captive portal.