HTTP Status Codes Reference
Complete reference for HTTP response status codes. Find meanings, descriptions, and RFC specifications.
OK
The request has succeeded. The meaning of the success depends on the HTTP method.
Created
The request has been fulfilled and resulted in a new resource being created.
Accepted
The request has been accepted for processing, but the processing has not been completed.
Non-Authoritative Information
The request was successful but the enclosed payload has been modified.
No Content
The server successfully processed the request and is not returning any content.
Reset Content
The server successfully processed the request, but 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.
Multiple Choices
The request has more than one possible response. User agent should choose one.
Moved Permanently
The URL of the requested resource has been changed permanently.
Found
The URI of requested resource has been changed temporarily.
See Other
The server sent this response to direct the client to get the requested resource with a GET request.
Not Modified
This is used for caching purposes. It tells the client that the response has not been modified.
Temporary Redirect
The server sends this response to direct the client to get the requested resource with same method.
Permanent Redirect
This means that the resource is now permanently located at another URI.
Bad Request
The server could not understand the request due to invalid syntax.
Unauthorized
The client must authenticate itself to get the requested response.
Payment Required
This response code is reserved for future use.
Forbidden
The client does not have access rights to the content.
Not Found
The server can not find the requested resource.
Method Not Allowed
The request method is known by the server but is not supported by the target resource.
Not Acceptable
This response is sent when the web server cannot find content that conforms to the criteria given by the user agent.
Proxy Authentication Required
This is similar to 401 but authentication is needed to be done by a proxy.
Request Timeout
This response is sent on an idle connection by some servers.
Conflict
This response is sent when a request conflicts with the current state of the server.
Gone
This response is sent when the requested content has been permanently deleted from server.
Length Required
The server rejected the request because the Content-Length header field is not defined.
Precondition Failed
The client has indicated preconditions in its headers which the server does not meet.
Payload Too Large
Request entity is larger than limits defined by server.
URI Too Long
The URI requested by the client is longer than the server is willing to interpret.
Unsupported Media Type
The media format of the requested data is not supported by the server.
Range Not Satisfiable
The range specified by the Range header field in the request can't be fulfilled.
Expectation Failed
This response code means the expectation indicated by the Expect request header field can't be met by the server.
I'm a teapot
The server refuses the attempt to brew coffee with a teapot.
Unprocessable Entity
The request was well-formed but was unable to be followed due to semantic errors.
Too Early
Indicates that the server is unwilling to risk processing a request that might be replayed.
Upgrade Required
The server refuses to perform the request using the current protocol.
Precondition Required
The origin server requires the request to be conditional.
Too Many Requests
The user has sent too many requests in a given amount of time.
Request Header Fields Too Large
The server is unwilling to process the request because either an individual header field is too large.
Unavailable For Legal Reasons
The user-agent requested a resource that cannot legally be provided.
Internal Server Error
The server has encountered a situation it doesn't know how to handle.
Not Implemented
The request method is not supported by the server and cannot be handled.
Bad Gateway
This error response means that the server got an invalid response while working as a gateway.
Service Unavailable
The server is not ready to handle the request.
Gateway Timeout
This error response is given when the server is acting as a gateway and cannot get a response in time.
HTTP Version Not Supported
The HTTP version used in the request is not supported by the server.
Variant Also Negotiates
The server has an internal configuration error.
Insufficient Storage
The server is unable to store the representation needed to complete the request.
Loop Detected
The server detected an infinite loop while processing the request.
Not Extended
Further extensions to the request are required for the server to fulfill it.
Network Authentication Required
The client needs to authenticate to gain network access.
1xx Informational
Request received, continuing process
2xx Success
Request was successfully received, understood, and accepted
3xx Redirection
Further action needs to be taken to complete the request
4xx Client Error
Request contains bad syntax or cannot be fulfilled
5xx Server Error
Server failed to fulfill a valid request