HTTP Status Code Reference
Complete reference for all HTTP status codes — descriptions, use cases, and common causes for every 1xx–5xx code
Continue
The server has received the request headers and the client should proceed to send the request body.
Use case: Used with large POST requests where the client sends Expect: 100-continue first.
Switching Protocols
The server agrees to switch protocols as requested by the client via the Upgrade header.
Use case: Used when upgrading from HTTP to WebSocket.
Processing
The server has received and is processing the request, but no response is available yet.
Use case: WebDAV: prevents the client from timing out on long-running requests.
Early Hints
Used to return some response headers before final HTTP message.
Use case: Allows browsers to start preloading resources while the server prepares the main response.
OK
The request has succeeded. The meaning depends on the HTTP method used.
Use case: Standard success response for GET, POST, PUT, PATCH requests.
Created
The request has succeeded and a new resource has been created as a result.
Use case: Returned after a successful POST that creates a new resource.
Accepted
The request has been accepted for processing, but the processing has not been completed.
Use case: Asynchronous operations like batch jobs or email sending.
Non-Authoritative Information
The returned metadata is not exactly the same as available from the origin server, but collected from a local or third-party copy.
Use case: Proxy servers that modify or annotate responses.
No Content
The server successfully processed the request but is not returning any content.
Use case: DELETE requests and PUT updates that don't need to return a body.
Reset Content
The server successfully processed the request and instructs the client to reset the document view.
Use case: After form submission where the form should be cleared.
Partial Content
The server is delivering only part of the resource due to a Range header in the request.
Use case: Video streaming and resumable file downloads.
Multi-Status
Provides status for multiple independent operations and may contain multiple response codes.
Use case: WebDAV operations that affect multiple resources.
Already Reported
The members of a DAV binding have already been enumerated in a preceding part of the response.
Use case: WebDAV to avoid enumerating internal members multiple times.
IM Used
The server has fulfilled a GET request for the resource and the response represents one or more instance-manipulations.
Use case: Delta encoding in HTTP for efficient content delivery.
Multiple Choices
The request has more than one possible response. The user agent should choose one of them.
Use case: Content negotiation when multiple formats are available.
Moved Permanently
The URL of the requested resource has been changed permanently. The new URL is given in the response.
Use case: Permanent URL redirects, passing SEO link equity to the new URL.
Found
The URI of requested resource has been changed temporarily. The client should use the same URI in future requests.
Use case: Temporary redirects, login redirects.
See Other
The response to the request can be found under another URI using a GET method.
Use case: Redirecting after a POST to prevent form resubmission (Post/Redirect/Get pattern).
Not Modified
There is no need to retransmit the requested resources. The client can use the cached version.
Use case: HTTP caching with ETag or Last-Modified headers.
Temporary Redirect
The request should be repeated with another URI but future requests should still use the original URI.
Use case: Temporary redirects that must preserve the HTTP method (unlike 302).
Permanent Redirect
The resource is now permanently located at another URI and the HTTP method must not change.
Use case: Permanent redirects that must preserve the HTTP method.
Bad Request
The server cannot or will not process the request due to a client error such as malformed request syntax or invalid parameters.
Use case: Invalid JSON body, missing required fields, malformed query parameters.
Unauthorized
The client must authenticate itself to get the requested response. Similar to 403 but authentication is expected.
Use case: Missing or invalid authentication token or API key.
Payment Required
Reserved for future use. Originally intended for digital payment systems.
Use case: Quota exceeded on a paid API, subscription required to access resource.
Forbidden
The client does not have access rights to the content — unlike 401, the client's identity is known but lacks permission.
Use case: Accessing admin-only resources, reading another user's private data.
Not Found
The server can not find the requested resource. The URL is not recognized.
Use case: Deleted pages, mistyped URLs, resources that don't exist.
Method Not Allowed
The request method is known by the server but is not supported by the target resource.
Use case: Sending a DELETE to a read-only endpoint, or POST to a GET-only route.
Not Acceptable
The server cannot produce a response matching the list of acceptable values defined in the request's proactive content negotiation headers.
Use case: Accept header requests a format the server can't provide.
Proxy Authentication Required
Authentication is needed to be done by a proxy. Similar to 401 but authentication should be performed by a proxy.
Use case: Corporate proxies requiring credentials before allowing internet access.
Request Timeout
The server would like to shut down this unused connection. It is sent on an idle connection by some servers.
Use case: Client takes too long to send the request body.
Conflict
The request conflicts with the current state of the server.
Use case: Duplicate entry creation, version conflicts in optimistic locking.
Gone
The requested content has been permanently deleted from the server with no forwarding address.
Use case: Permanently deleted resources where the deletion should be cached by clients.
Length Required
The server rejected the request because the Content-Length header field is not defined.
Use case: Server requires Content-Length for POST/PUT requests.
Precondition Failed
The client has indicated preconditions in its headers which the server does not meet.
Use case: Conditional requests with If-Match or If-Unmodified-Since that fail.
Payload Too Large
The request entity is larger than limits defined by the server.
Use case: File uploads exceeding the server's maximum allowed size.
URI Too Long
The URI requested by the client is longer than the server is willing to interpret.
Use case: Extremely long query strings, typically from very large form GET submissions.
Unsupported Media Type
The media format of the requested data is not supported by the server.
Use case: Sending XML to an endpoint that only accepts JSON.
Range Not Satisfiable
The range specified by the Range header field in the request can't be fulfilled.
Use case: Requesting a byte range beyond the end of a file.
Expectation Failed
The expectation indicated by the Expect request header field can't be met by the server.
Use case: Server cannot fulfill the Expect: 100-continue header.
I'm a Teapot
The server refuses the attempt to brew coffee with a teapot. (April Fools RFC 2324)
Use case: Easter egg in many APIs; sometimes used for intentionally unimplemented endpoints.
Unprocessable Entity
The request was well-formed but was unable to be followed due to semantic errors.
Use case: Validation errors — request is syntactically valid JSON but fails business rules.
Locked
The resource that is being accessed is locked.
Use case: WebDAV: resource is checked out by another user.
Failed Dependency
The request failed due to failure of a previous request.
Use case: WebDAV: a required prior operation failed.
Too Early
The server is unwilling to risk processing a request that might be replayed.
Use case: TLS 1.3 early data (0-RTT) that could be replayed by an attacker.
Upgrade Required
The server refuses to perform the request using the current protocol but might be willing to do so after the client upgrades.
Use case: Forcing clients to use HTTPS or a newer protocol version.
Precondition Required
The origin server requires the request to be conditional.
Use case: Preventing lost update problems by requiring ETags on PUT requests.
Too Many Requests
The user has sent too many requests in a given amount of time (rate limiting).
Use case: API rate limiting — client has exceeded their request quota.
Request Header Fields Too Large
The server is unwilling to process the request because its header fields are too large.
Use case: Overly large cookies or many custom headers exceed the server's limits.
Unavailable For Legal Reasons
The server is denying access to the resource as a consequence of a legal demand.
Use case: GDPR takedowns, copyright enforcement, government-mandated censorship.
Internal Server Error
The server has encountered a situation it doesn't know how to handle. Generic catch-all for server-side errors.
Use case: Unhandled exceptions, database connection failures, unexpected bugs.
Not Implemented
The request method is not supported by the server and cannot be handled.
Use case: Server does not recognize or support the HTTP method used.
Bad Gateway
The server, while working as a gateway to get a response, got an invalid response.
Use case: Upstream server is down or returning invalid responses through a proxy or load balancer.
Service Unavailable
The server is not ready to handle the request. Common causes: maintenance downtime or server overload.
Use case: Server is under maintenance, overloaded, or starting up.
Gateway Timeout
The server is acting as a gateway and cannot get a response in time from the upstream server.
Use case: Slow database queries, external API timeouts, overloaded microservices.
HTTP Version Not Supported
The HTTP version used in the request is not supported by the server.
Use case: Client uses HTTP/3 but server only supports HTTP/1.1 and HTTP/2.
Variant Also Negotiates
The server has an internal configuration error with transparent content negotiation.
Use case: Server misconfiguration in content negotiation circular references.
Insufficient Storage
The method could not be performed on the resource because the server is unable to store the representation needed to complete the request.
Use case: WebDAV: server disk is full.
Loop Detected
The server detected an infinite loop while processing the request.
Use case: WebDAV: circular references in a Depth: infinity request.
Not Extended
Further extensions to the request are required for the server to fulfill it.
Use case: Client must send additional extension declarations the server requires.
Network Authentication Required
Indicates that the client needs to authenticate to gain network access.
Use case: Captive portals in hotels, airports, and coffee shops requiring login.
Continuer à explorer
Autres outils Développement qui pourraient vous plaire…
Formateur JSON
Formatez et validez du JSON avec coloration syntaxique
Base64 encoder/décoder
Encode et décode des chaînes Base64
URL Encoder/Decoder
Encode and decode URL components and query strings
Générateur UUID
Génère des identifiants UUID uniques
Hash Generator
Generate MD5, SHA-1, SHA-256, and SHA-512 hashes from text
Regex Tester
Test and debug regular expressions with match highlighting
JWT Decoder
Decode and inspect JWT token header and payload
HTML Formatter
Beautify and format HTML code with proper indentation