HTTP Status Codes
Free online HTTP status code reference. Browse and search all HTTP response codes with descriptions. 100% client-side.
The server has received the request headers and the client should proceed to send the body.
The requester has asked the server to switch protocols and the server has agreed.
The server has received and is processing the request, but no response is available yet.
The request has succeeded. The meaning depends on the HTTP method used.
The request has been fulfilled and a new resource has been created.
The request has been accepted for processing, but the processing has not been completed.
The server successfully processed the request but is not returning any content.
The server is delivering only part of the resource due to a range header sent by the client.
The request has more than one possible response. The user should choose one.
The requested resource has been permanently moved to a new URL.
The requested resource has been temporarily moved to a different URL.
The response to the request can be found under a different URI.
The resource has not been modified since the version specified by the request headers.
The request should be repeated with another URI, but future requests should still use the original URI.
The request and all future requests should be repeated using another URI.
The server cannot process the request due to a client error (malformed syntax, etc.).
The request requires user authentication. The client must authenticate itself.
Reserved for future use. Originally intended for digital payment systems.
The server understood the request but refuses to authorize it.
The server cannot find the requested resource. The most common HTTP error.
The request method is known by the server but not supported for the target resource.
The server cannot produce a response matching the list of acceptable values defined in the request.
The client must first authenticate itself with the proxy.
The server timed out waiting for the request.
The request conflicts with the current state of the server.
The requested resource is no longer available and will not be available again.
The server refuses to accept the request without a defined Content-Length header.
One or more conditions given in the request header fields evaluated to false.
The request entity is larger than the server is willing or able to process.
The URI requested by the client is longer than the server is willing to interpret.
The server refuses to accept the request because the payload format is unsupported.
The range specified by the Range header cannot be satisfied.
The expectation given in the Expect request header could not be met.
The server refuses the attempt to brew coffee with a teapot.
The server understands the content type but cannot process the instructions.
The server is unwilling to risk processing a request that might be replayed.
The server refuses to perform the request using the current protocol.
The user has sent too many requests in a given amount of time (rate limiting).
The server is unwilling to process the request because header fields are too large.
The requested resource is unavailable due to legal demands.
The server encountered an unexpected condition that prevented it from fulfilling the request.
The server does not support the functionality required to fulfill the request.
The server received an invalid response from an upstream server while acting as a gateway.
The server is not ready to handle the request (overloaded or down for maintenance).
The server did not receive a timely response from an upstream server.
The server does not support the HTTP protocol version used in the request.
The server is unable to store the representation needed to complete the request.
The client needs to authenticate to gain network access (captive portal).