HTTP Status Code Reference
IANA status code registry · Snapshot dated
Check a saved response
64 matching status codes
100 Continue
The server asks the client to continue sending the request.
A client sends Expect: 100-continue before uploading a large request body.
101 Switching Protocols
The server accepted a request to switch protocols.
An HTTP/1.1 server returns this after accepting a WebSocket upgrade.
102 Processing
The WebDAV server has received a request and is still working on it.
A long WebDAV action sends an interim status while processing.
103 Early Hints
An interim response advertises hints before the final response.
A page response sends Link preload hints while its main response is being prepared.
104 Upload Resumption Supported (Temporary)
The resumable-upload draft used this interim status to signal support.
An experimental upload capture can show 104 before a final response. This dated snapshot preserves the temporary entry with its listed expiry of 2026-11-13. Check IANA for subsequent registrations.
200 OK
The request succeeded. Its response meaning depends on the method.
A GET for a product returns its current representation.
201 Created
The request created one or more resources.
A POST creates an order and returns its URL in Location.
202 Accepted
The request was accepted for processing, which can finish later.
An import endpoint queues a job and returns a status URL.
203 Non-Authoritative Information
A transforming intermediary modified a successful origin response.
A proxy changes a representation before returning it.
204 No Content
The request succeeded and the response has no content.
A successful DELETE completes without returning a representation.
205 Reset Content
The server asks the client to reset the document view after a successful request.
A form handler accepts input and requests a fresh form state.
206 Partial Content
The server supplied one or more ranges of the representation.
A media player requests a file segment and receives Content-Range.
207 Multi-Status
A WebDAV body reports results for multiple resources.
A collection operation returns per-item results in a multistatus body.
208 Already Reported
A WebDAV multistatus body marks a binding already reported elsewhere.
Processing a collection with repeated bindings lists members once.
226 IM Used
The response reflects one or more applied instance manipulations.
A client that requested delta encoding receives a response based on its cached copy.
300 Multiple Choices
The target has multiple representation choices the client can select.
A resource advertises its available document formats.
301 Moved Permanently
The resource has a permanent new URI. A client may change POST to GET.
After a site move, an old article URI points to a lasting new one.
302 Found
The resource is temporarily available under another URI. A client may change POST to GET.
A temporarily relocated catalog points users to an alternate path.
303 See Other
The server points the client to another resource to retrieve.
After POST creates a job, Location points to a status page to read with GET.
304 Not Modified
The client's conditional GET or HEAD can use its existing cached representation.
If-None-Match matches the current ETag, so the body need not be transferred again.
305 Use Proxy
Historically instructed a client to use a proxy. RFC 9110 deprecates it.
An old capture may contain this status when directing a client to a proxy.
306 (Unused)
RFC 9110 reserves this code and leaves it unused.
An encountered 306 needs context from the actual emitting system.
307 Temporary Redirect
The target is temporarily elsewhere. An automatic redirect preserves the request method.
A POST temporarily redirected to another path stays a POST.
308 Permanent Redirect
The target has moved permanently. An automatic redirect preserves the request method.
A permanently relocated upload endpoint receives the same method at its new URI.
400 Bad Request
The server cannot or will not process a request it treats as erroneous.
A server rejects malformed HTTP framing.
401 Unauthorized
The request lacks valid authentication credentials for the target resource.
An API sends WWW-Authenticate after a request arrives without a valid token.
402 Payment Required
RFC 9110 reserves this response for future use.
An API may document a provider-specific payment meaning for 402.
403 Forbidden
The server understood the request and refuses to fulfill it.
A request uses valid credentials that lack permission for the target.
404 Not Found
The server found no current representation or chose to conceal one.
A request names an article with no matching route.
405 Method Not Allowed
The method is known to the server and unsupported for this target.
A response to DELETE includes Allow: GET, HEAD for a read-only resource.
406 Not Acceptable
The server cannot provide a representation acceptable under the request's negotiation fields.
A client accepts only XML while the API offers only JSON.
407 Proxy Authentication Required
A proxy requires valid authentication from the client.
An authenticated gateway sends Proxy-Authenticate before relaying traffic.
408 Request Timeout
The server did not receive a complete request in the time it allowed.
A connection stalled while the client was sending the request.
409 Conflict
The request conflicts with the target's current state.
An API rejects a change to a record that is already closed.
410 Gone
The resource is gone and that condition is expected to be permanent.
A retired document endpoint indicates its removal is deliberate.
411 Length Required
The server refuses the request without a defined Content-Length.
An upload service requires the client to declare the request size.
412 Precondition Failed
A precondition supplied in the request evaluated to false.
A stale If-Match value prevents overwriting a newer document.
413 Content Too Large
The request content exceeds what the server accepts.
An upload exceeds the server's file size limit.
414 URI Too Long
The URI exceeds what the server is willing to interpret.
An application puts a substantial data payload in the request URL.
415 Unsupported Media Type
The target rejects the request content's media type or encoding.
An endpoint configured for JSON receives XML.
416 Range Not Satisfiable
The requested ranges cannot be served.
A byte range starts beyond the end of a file.
417 Expectation Failed
At least one expectation in the request's Expect field cannot be met.
An intermediary cannot honor an expectation sent by the client.
418 (Unused)
RFC 9110 reserves this code as unused. Historical references call it I'm a teapot.
A test endpoint may still emit the historical joke response.
421 Misdirected Request
The server cannot or will not provide an authoritative response for the URI.
A request reaches the wrong origin on a reused connection.
422 Unprocessable Content
The media type and syntax are understood but the contained instructions cannot be processed.
A syntactically valid update contains a date outside the allowed range.
423 Locked
A WebDAV source or destination is locked.
An editor tries to save a locked document without the required lock token.
424 Failed Dependency
An action depended on another action that failed.
A WebDAV property operation reports a dependent change that could not proceed.
425 Too Early
The server declines to risk processing a request that might be replayed.
A server rejects TLS early data and expects a retry after the handshake.
426 Upgrade Required
The server requires a protocol upgrade before serving the request.
A response includes Upgrade to advertise the supported protocol.
428 Precondition Required
The server requires a conditional request.
An editing API asks the client to include If-Match to avoid overwriting newer data.
429 Too Many Requests
The server reports a request rate limit.
A throttled API includes Retry-After with a delay in seconds.
431 Request Header Fields Too Large
One or more request header fields are too large.
A very large Cookie field pushes the request over the header size limit.
451 Unavailable For Legal Reasons
The response reports that a legal demand prevents providing the resource.
A publisher sends the status for a resource it was required to restrict.
500 Internal Server Error
An unexpected server condition prevented completing the request.
An internal application exception aborts the response.
501 Not Implemented
The server lacks functionality needed to fulfill the request.
A server does not implement the method at all.
502 Bad Gateway
A gateway or proxy obtained an invalid response from an upstream server.
A reverse proxy receives a malformed upstream response.
503 Service Unavailable
The service is temporarily unable to handle the request.
A service in maintenance sends Retry-After to suggest when to retry.
504 Gateway Timeout
A gateway or proxy did not receive an upstream response in time.
An API gateway reaches its backend timeout while waiting for a worker.
505 HTTP Version Not Supported
The server does not support or refuses the HTTP major version used.
A server declines a request using a major HTTP version it cannot handle.
506 Variant Also Negotiates
A negotiated variant is configured to negotiate itself.
A language variant points back into transparent content negotiation.
507 Insufficient Storage
The server cannot store the representation required to complete the request.
A WebDAV server lacks capacity to finish a file upload.
508 Loop Detected
The server detected a loop while processing the request.
A depth-wide WebDAV operation encounters a cycle in resource bindings.
510 Not Extended (OBSOLETED)
The historic HTTP Extension Framework used this status for missing extensions.
A legacy capture can show 510 when that framework required additional extension information.
511 Network Authentication Required
An intermediary indicates that network access requires authentication.
A captive portal tells a client to authenticate before using the network.