Comprehensive guide to HTTP status codes with detailed explanations, common causes, and practical solutions for developers and system administrators.
Showing 63 of 63 status codes
The server has received the request headers and the client should proceed to send the request body.
The server is switching protocols as requested by the client.
The server has received and is processing the request, but no response is available yet.
Used to return some response headers before final HTTP message.
The request has succeeded and the server has returned the requested data.
The request has been fulfilled and a new resource has been created.
The request has been accepted for processing, but processing is not complete.
The server is returning information from a third party rather than the origin server.
The request was successful but there is no content to return.
The server has fulfilled the request and the user agent should reset the document view.
The server is delivering only part of the resource due to a range header sent by the client.
The message body contains multiple separate response codes for different operations.
The members of a DAV binding have already been enumerated in a previous reply.
The server has fulfilled a request for the resource and the response represents the result of instance manipulations.
The request has more than one possible response and 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 another URI using the GET method.
The resource has not been modified since the last request and can be served from cache.
The requested resource must be accessed through the proxy specified in the Location header.
This status code is no longer used but is reserved for future use.
The request should be repeated with another URI but future requests should use the original URI.
The request and all future requests should be repeated using another URI.
The server cannot process the request due to invalid syntax or malformed request.
Authentication is required and has failed or has not been provided.
Reserved for future use. Originally intended for digital payment systems.
The server understands the request but refuses to authorize it.
The requested resource could not be found on the server.
The request method is not supported for the requested resource.
The server cannot produce a response matching the list of acceptable values.
Authentication with the proxy server is required.
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 request did not specify the length of its content.
One or more conditions given in the request header fields evaluated to false.
The request entity is larger than limits defined by server.
The URI requested by the client is longer than the server can interpret.
The media format of the requested data is not supported.
The range specified by the Range header field cannot be fulfilled.
The expectation indicated by the Expect request header field cannot be met.
The server refuses the attempt to brew coffee with a teapot (RFC 2324).
The request was directed at a server that is not able to produce a response.
The request was well-formed but contains semantic errors.
The resource that is being accessed is locked.
The request failed because it depended on another request that failed.
The server is unwilling to risk processing a request that might be replayed.
The client should switch to a different protocol.
The origin server requires the request to be conditional.
The user has sent too many requests in a given amount of time.
The server is unwilling to process the request because header fields are too large.
The server is denying access to the resource for legal reasons.
The server has encountered a situation it doesn't know how to handle.
The request method is not supported by the server and cannot be handled.
The server received an invalid response from the upstream server.
The server is not ready to handle the request, often due to maintenance or overload.
The server did not receive a timely response from the upstream server.
The HTTP version used in the request is not supported by the server.
The server has an internal configuration error.
The server is unable to store the representation needed to complete the request.
The server detected an infinite loop while processing the request.
Further extensions to the request are required for the server to fulfill it.
The client needs to authenticate to gain network access.