HTTP Status Codes
Informational Codes (1--)
100 Continue
Indicates that the initial part of a request has been received and the client should continue with the request.
101 Switching Protocols
Informs the client that the server is switching protocols as requested by the client.
102 Processing
The server has received and is processing the request, but no response is available yet.
103 Early Hints
The server is suggesting the client pre-load resources while the main response is still being generated.
Success Codes (2--)
200 OK
The request was successful, and the server returned the requested data.
201 Created
The request was successful, and a new resource has been created.
202 Accepted
The request has been accepted for processing, but the processing is not complete.
203 Non-Authoritative Information
The server successfully processed the request, but is returning modified metadata.
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 the client 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
Provides status for multiple independent operations in a single response.
208 Already Reported
Used in WebDAV to indicate that a particular set of properties have already been reported.
226 IM Used
Indicates that the server has fulfilled a request for the resource and the response is a representation of the result of one or more instance-manipulations applied to the current instance.
Redirection Codes (3--)
300 Multiple Choices
The request has more than one possible response, and the client should choose one.
301 Moved Permanently
The requested resource has been permanently moved to a new URL.
302 Found
The requested resource is temporarily located at a different URL.
303 See Other
The response to the request can be found at another URL, using the GET method.
304 Not Modified
Indicates that the resource has not been modified since the last request, so the cached version can be used.
305 Use Proxy
The requested resource is available only through a proxy.
307 Temporary Redirect
The requested resource is temporarily located at a different URL, and the client should repeat the request at that URL.
308 Permanent Redirect
Similar to 301, but indicates that the request method must not change when redirecting.
Client Error Codes (4--)
400 Bad Request
The server cannot process the request due to a client error (e.g., malformed request syntax).
401 Unauthorized
Authentication is required and has failed or not been provided.
402 Payment Required
Reserved for future use; originally intended for payment schemes.
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 allowed for the requested resource.
406 Not Acceptable
The server cannot produce a response matching the list of acceptable values defined in the request.
407 Proxy Authentication Required
The client must first authenticate itself with the proxy.
408 Request Timeout
The server timed out waiting for the request from the client.
409 Conflict
The request could not be completed due to a conflict with the current state of the resource.
410 Gone
The requested resource is no longer available on the server and no forwarding address is known.
411 Length Required
The server refuses to accept the request without a defined Content-Length.
412 Precondition Failed
The server does not meet one of the preconditions specified by the client.
413 Payload Too Large
The request entity is larger than the server is willing or able to process.
414 URI Too Long
The request URI is longer than the server is willing to interpret.
415 Unsupported Media Type
The media type of the request data is not supported by the server.
416 Range Not Satisfiable
The requested range cannot be satisfied by the server.
417 Expectation Failed
The server cannot meet the requirements of the Expect request-header field.
418 I'm a Teapot
The server is not able to brew the requested coffee because it is, in fact, a teapot. Note that a combined coffee/teapot that is temporarily out of coffee shoudl instead return 503.
426 Upgrade Required
The client should switch to a different protocol as indicated by the server.
428 Precondition Required
The origin server requires the request to be conditional.
429 Too Many Requests
The user has sent too many requests in a given amount of time.
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 user has been blocked from accessing the resource for legal reasons.
Server Error Codes (5--)
500 Internal Server Error
An unexpected condition was encountered on the server, preventing it from fulfilling the request.
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 an upstream server while acting as a gateway.
503 Service Unavailable
The server is currently unable to handle the request due to temporary overload or maintenance.
504 Gateway Timeout
The server did not receive a timely response from an upstream server while acting as a gateway.
505 HTTP Version Not Supported
The server does not support the HTTP protocol version that was used in the request.
511 Network Authentication Required
The client needs to authenticate to gain network access.