HTTP Status Codes Reference
A comprehensive demo for the http-status-lite npm package. Browse, search, and copy HTTP status codes with ease.
Showing 62 of 62 status codes
Server has received the request headers and client should proceed to send the body
Example Usage:
Used for large uploads to avoid sending body if headers are rejected
Server agrees to switch to the protocol requested by the client
Example Usage:
Commonly used for WebSocket upgrades
Server has received and is processing the request, but no response is available yet
Example Usage:
Used for long-running operations with WebDAV
Server sends preliminary headers to allow client to start loading resources
Example Usage:
Preload CSS or JavaScript before final response
Request succeeded and the response body contains the requested resource
Example Usage:
Standard response for successful GET, PUT, or POST requests
Request succeeded and a new resource was created
Example Usage:
Returned after successfully creating a new user or post
Request has been accepted for processing but is not yet complete
Example Usage:
Used for asynchronous operations like batch processing
Request succeeded but the returned information may be from a cached or third-party source
Example Usage:
Proxy servers may return this with cached content
Request succeeded but there is no content to return
Example Usage:
Common response for successful DELETE requests
Request succeeded and the client should reset the document view
Example Usage:
Used to clear form inputs after submission
Server is delivering only part of the resource due to a range request
Example Usage:
Video streaming with range headers for seeking
Response body contains status for multiple operations in a WebDAV request
Example Usage:
WebDAV operations affecting multiple resources
Members of a DAV binding have already been enumerated in a previous response
Example Usage:
WebDAV binding optimization
Server has fulfilled a GET request for the resource and the response is a representation of the instance-manipulation result
Example Usage:
Delta encoding and instance manipulation
Request has multiple possible responses and the client should choose one
Example Usage:
Content negotiation with multiple format options
Resource has been permanently moved to a new URL
Example Usage:
SEO-friendly URL changes, HTTP to HTTPS migration
Resource has been temporarily moved to a different URL
Example Usage:
Temporary redirects during maintenance
Redirect to a different URL using GET method
Example Usage:
Post-Redirect-Get pattern after form submission
Resource has not been modified since the last request
Example Usage:
Browser caching with If-Modified-Since header
Request must be made through a proxy
Example Usage:
Deprecated due to security concerns
Resource has been temporarily moved, preserving the original HTTP method
Example Usage:
Temporary URL changes while maintaining POST data
Resource has been permanently moved, preserving the original HTTP method
Example Usage:
Permanent URL changes while maintaining request method
Server cannot process the request due to invalid syntax or malformed structure
Example Usage:
Missing required fields or invalid JSON
Authentication is required and has failed or not been provided
Example Usage:
Missing or invalid JWT token
Payment is required to access the resource
Example Usage:
Subscription-based APIs or pay-per-use services
Server understands the request but refuses to authorize it
Example Usage:
User lacks permission for the requested resource
Server cannot find the requested resource
Example Usage:
Accessing a non-existent user or post
Request method is not supported for the target resource
Example Usage:
Sending POST to a read-only endpoint
Server cannot produce a response matching the Accept headers
Example Usage:
Client requests XML but server only supports JSON
Authentication with a proxy is required
Example Usage:
Corporate proxy requiring credentials
Server timed out waiting for the request
Example Usage:
Client took too long to send request body
Request conflicts with the current state of the server
Example Usage:
Duplicate resource or version conflict
Resource has been permanently deleted and will not be restored
Example Usage:
Intentionally removed content
Request is missing the Content-Length header
Example Usage:
POST request without Content-Length
One or more conditions in the request headers failed
Example Usage:
If-Match or If-Unmodified-Since header mismatch
Request body exceeds the server size limit
Example Usage:
Uploading a file larger than the configured maximum
Request URI exceeds the server length limit
Example Usage:
Extremely long query parameters
Media type of the request body is not supported
Example Usage:
Sending XML to an endpoint that only accepts JSON
Requested range is invalid or cannot be served
Example Usage:
Requesting bytes beyond file length
Server cannot meet the Expect header requirement
Example Usage:
Client expects 100-continue but server refuses
Server refuses to brew coffee because it is a teapot (RFC 2324 April Fools joke)
Example Usage:
Easter egg response in APIs
Request was directed at a server that cannot produce a response
Example Usage:
HTTP/2 connection reuse issues
Request is well-formed but contains semantic errors
Example Usage:
Validation errors in form data
Resource is locked and cannot be accessed
Example Usage:
WebDAV file locking
Request failed due to a previous failed request
Example Usage:
WebDAV operation depending on prior success
Server is unwilling to process due to potential replay attack
Example Usage:
TLS early data rejection
Server requires an upgrade to a different protocol
Example Usage:
HTTP/1.1 to HTTP/2 upgrade
Server requires the request to be conditional
Example Usage:
Requiring If-Match header for updates
Client has sent too many requests in a given time period
Example Usage:
Rate limiting response
Request headers exceed the server limit
Example Usage:
Too many cookies or large Authorization header
Resource is unavailable due to legal demands
Example Usage:
Censored or legally restricted content
Server encountered an unexpected condition that prevented it from fulfilling the request
Example Usage:
Unhandled exception or database connection failure
Server does not support the functionality required to fulfill the request
Example Usage:
Unsupported HTTP method
Server received an invalid response from an upstream server
Example Usage:
Reverse proxy cannot reach backend server
Server is temporarily unable to handle the request
Example Usage:
Maintenance mode or server overload
Server did not receive a timely response from an upstream server
Example Usage:
Proxy timeout waiting for backend
Server does not support the HTTP version used in the request
Example Usage:
HTTP/2 request to HTTP/1.1 only server
Server has an internal configuration error in content negotiation
Example Usage:
Transparent content negotiation loop
Server is unable to store the representation needed to complete the request
Example Usage:
WebDAV storage quota exceeded
Server detected an infinite loop while processing the request
Example Usage:
WebDAV binding loop
Further extensions to the request are required
Example Usage:
Missing required extension header
Client needs to authenticate to gain network access
Example Usage:
Captive portal login page