HTTP Status Codes
Quick reference for HTTP status code meanings and usage.
HTTP Status Codes Directory
Server received request headers; client should continue sending the body.
Server agrees to switch protocols, commonly for WebSocket.
Server has received and is processing the request.
Provides early hints to preload resources.
Request succeeded and returned a resource.
Request succeeded and created a new resource.
Request accepted but not yet processed.
Returned metadata comes from a local or third-party copy.
Request succeeded but returns no content.
Request succeeded and the client should reset the current document view.
Server successfully fulfilled a range request.
WebDAV response containing multiple independent status codes.
WebDAV response avoiding repeated enumeration of already reported members.
Server fulfilled a GET request using instance manipulations.
Requested resource has multiple available representations.
Resource has moved permanently to a new URL.
Resource temporarily resides at a different URL.
Response can be found at another URI using GET.
Resource not modified; use cached version.
Deprecated status code indicating the resource must be accessed through a proxy.
Temporary redirect, same method should be used.
Permanent redirect, same method should be used.
Malformed request or invalid parameters.
Authentication required or token invalid.
Server understands but refuses the request.
Requested resource was not found.
HTTP method not allowed for this resource.
Server cannot provide a representation matching the request headers.
Client must authenticate with the proxy before proceeding.
Server timed out waiting for the request.
Request conflicts with current resource state.
Resource is permanently gone.
Server requires a valid Content-Length header.
One or more preconditions in the request headers failed.
Request payload exceeds server limits.
Request URI is too long for the server.
Request media type is not supported.
Requested Range cannot be fulfilled for the target resource.
RFC 2324 April Fools easter egg, not a formal standard.
Request was directed to a server that cannot process it.
Request is well-formed but semantically incorrect.
WebDAV resource is locked and cannot be accessed as requested.
WebDAV request failed because a dependent action failed.
Server is unwilling to process a request that might be replayed.
Client must switch to a different protocol before retrying.
Server requires the request to be conditional to avoid conflicts.
Rate limit has been exceeded.
Request header fields are too large for the server to process.
Resource access denied due to legal reasons.
Server encountered an unexpected error.
Server does not support this functionality.
Invalid response from upstream server.
Server temporarily unavailable or overloaded.
Upstream server failed to respond in time.
Server does not support the HTTP version.
Server has a configuration error causing circular content negotiation.
Server cannot store the data needed to complete the request.
WebDAV server detected an infinite loop while processing the request.
Server requires further extensions to fulfill the request.
Client needs to authenticate to gain network access.
About This Tool
The HTTP status codes reference provides explanations and usage scenarios for common 1xx–5xx responses. Filter by category or search by code/keyword, and copy the code with name in one click—perfect for API integration, log troubleshooting, and quick reference.
Features
- 🔎 Keyword search for codes and meanings
- 🧭 Category filter for 1xx–5xx groups
- 📋 One-click copy for code and name
- 🌐 Bilingual descriptions in Chinese and English
- 🔒 Local-only processing with no uploads