HTTP Status Code Reference
Search and browse the complete IANA HTTP status code registry (1xx through 5xx).
Showing 63 of 63 status codes.
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.
Processing
The server has received and is processing the request, but no response is available yet (WebDAV).
Early Hints
Used to return some response headers before the final HTTP message.
OK
The request has succeeded. The meaning depends on the HTTP method used.
Created
The request has been fulfilled and a new resource has been created.
Accepted
The request has been accepted for processing, but the processing has not been completed.
Non-Authoritative Information
The returned metadata is not from the origin server but a local or third-party copy.
No Content
The server has fulfilled the request but does not need to return an entity-body.
Reset Content
The server has fulfilled the request and the user agent should reset the document view.
Partial Content
The server has fulfilled the partial GET request for a resource (Range request).
Multi-Status
Conveys information about multiple resources for WebDAV operations in a single XML response.
Already Reported
Used inside a DAV: propstat response to avoid enumerating members of the same collection twice (WebDAV).
IM Used
The server has fulfilled a GET request and the response represents the result of instance-manipulations.
Multiple Choices
The request has more than one possible response, each with its own location and agent-driven negotiation.
Moved Permanently
The target resource has been assigned a new permanent URI; future references should use that URI.
Found
The target resource resides temporarily under a different URI. Clients should continue to use the original URI.
See Other
The server is redirecting the user agent to a different resource, fetched with GET.
Not Modified
Indicates that a conditional GET request has been received and would have resulted in a 200 response if not for the condition.
Use Proxy
Defined in a previous version of the HTTP specification to indicate the requested resource must be accessed through a proxy. Deprecated.
Unused
No longer used; reserved. Was defined as "Switch Proxy" in a previous HTTP specification.
Temporary Redirect
The target resource resides temporarily under a different URI; the method must not change.
Permanent Redirect
The target resource has been assigned a new permanent URI; the method must not change.
Bad Request
The server cannot process the request due to malformed syntax.
Unauthorized
The request requires user authentication.
Payment Required
Reserved for future use. Sometimes used for digital payment systems.
Forbidden
The server understood the request but refuses to authorize it.
Not Found
The server has not found anything matching the Request-URI.
Method Not Allowed
The method specified in the request is not allowed for the resource identified by the Request-URI.
Not Acceptable
The resource is only capable of generating content not acceptable according to the Accept headers.
Proxy Authentication Required
The client must first authenticate itself with the proxy.
Request Timeout
The server timed out waiting for the request from the client.
Conflict
The request could not be completed due to a conflict with the current state of the resource.
Gone
The resource is no longer available and no forwarding address is known.
Length Required
The request requires a valid Content-Length header.
Precondition Failed
A precondition given in the request headers evaluated to false.
Payload Too Large
The server is refusing to process a request because the request payload is larger than the server is willing to process.
URI Too Long
The server is refusing to service the request because the request-target is longer than the server is willing to interpret.
Unsupported Media Type
The server is refusing to service the request because the entity is in a format not supported by the requested method.
Range Not Satisfiable
The Range header value in the request does not overlap the extent of the selected resource.
Expectation Failed
The expectation given in the Expect header could not be met by the server.
I'm a Teapot
Any attempt to brew coffee with a teapot should result in the error code "418 I'm a Teapot" (RFC 2324).
Misdirected Request
The request was directed at a server that is not able to produce a response.
Unprocessable Entity
The server understands the content type but was unable to process the contained instructions (WebDAV).
Locked
The source or destination resource of a method is locked (WebDAV).
Failed Dependency
The method could not be performed because the requested action depended on another action that failed (WebDAV).
Too Early
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; the client must upgrade.
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 (rate limiting).
Request Header Fields Too Large
The server is unwilling to process the request because its header fields are too large.
Unavailable For Legal Reasons
The server is denying access to the resource as a consequence of a legal demand.
Internal Server Error
The server encountered an unexpected condition that prevented it from fulfilling the request.
Not Implemented
The server does not support the functionality required to fulfill the request.
Bad Gateway
The server, while acting as a gateway or proxy, received an invalid response from an upstream server.
Service Unavailable
The server is currently unable to handle the request due to temporary overloading or maintenance.
Gateway Timeout
The server, while acting as a gateway or proxy, did not receive a timely response from the upstream server.
HTTP Version Not Supported
The server does not support the HTTP protocol version that was used in the request.
Variant Also Negotiates
Transparent content negotiation for the request results in a circular reference.
Insufficient Storage
The method could not be performed on the resource because the server is unable to store the representation (WebDAV).
Loop Detected
The server detected an infinite loop while processing the request (WebDAV).
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 (captive portals).