HTTP Status & Headers Reference
Git & WorkflowSearchable reference directory for HTTP status codes, specifications, and standard request/response headers.
Continue
The server has received the request headers and the client should proceed to send the request body.
Switching Protocols
The requester has asked the server to switch protocols and the server has agreed to do so.
Processing
An interim response used to inform the client that the server has accepted the complete request, but has not yet completed it.
Early Hints
Used to return some response headers before final HTTP message (e.g. Preload links).
OK
Standard response for successful HTTP requests.
Created
The request has been fulfilled, resulting in the creation of a new resource.
Accepted
The request has been accepted for processing, but the processing has not been completed.
No Content
The server successfully processed the request, and is not returning any content.
Partial Content
The server is delivering only part of the resource due to a Range header sent by the client.
Moved Permanently
This and all future requests should be directed to the given URI.
Found (Moved Temporarily)
Tells the client to look at another URL, but future requests should still use the original URI.
Not Modified
Indicates that the resource has not been modified since the version specified by the request headers.
Temporary Redirect
In this case, the request should be repeated with another URI; however, future requests should still use the original URI. The request method MUST NOT change.
Permanent Redirect
The request and all future requests should be repeated using another URI. The request method MUST NOT change.
Bad Request
The server cannot or will not process the request due to an apparent client error.
Unauthorized
Authentication is required and has failed or has not yet been provided.
Forbidden
The request was valid, but the server is refusing action. The user might not have the necessary permissions for a resource.
Not Found
The requested resource could not be found but may be available in the future.
Method Not Allowed
A request method is not supported for the requested resource (e.g. GET on a form requiring POST).
Request Timeout
The server timed out waiting for the request.
Conflict
Indicates that the request could not be processed because of conflict in the current state of the resource.
Gone
Indicates that the resource requested was previously available at the URI, but is no longer available and will not be available again.
Payload Too Large
The request is larger than the server is willing or able to process.
Unsupported Media Type
The request entity has a media type which the server or resource does not support.
Unprocessable Entity
The request was well-formed but was unable to be followed due to semantic errors.
Too Many Requests
The user has sent too many requests in a given amount of time (rate limiting).
Internal Server Error
A generic error message, given when an unexpected condition was encountered and no more specific message is suitable.
Not Implemented
The server either does not recognize the request method, or it lacks the ability to fulfil the request.
Bad Gateway
The server was acting as a gateway or proxy and received an invalid response from the upstream server.
Service Unavailable
The server cannot handle the request (because it is overloaded or down for maintenance).
Gateway Timeout
The server was acting as a gateway or proxy and did not receive a timely response from the upstream server.