| 100 | Continue | The server received the request headers; the client should send the body. | Sent when the client used Expect: 100-continue before uploading a large body. |
| 101 | Switching Protocols | The server is switching to the protocol the client asked for in the Upgrade header. | Normal when opening a WebSocket connection. |
| 102 | Processing | WebDAV: the server has accepted the request but hasn’t finished. | Deprecated; rarely seen today. |
| 103 | Early Hints | Preliminary headers, usually Link preloads, sent before the final response. | Lets browsers start loading CSS and fonts while the server is still working. |
| 200 | OK | The request succeeded. | The standard success response for GET, and for POST or PUT that return a body. |
| 201 | Created | A new resource was created. | Return it from POST; include a Location header pointing at the new resource. |
| 202 | Accepted | The request was accepted for processing, but isn’t finished. | Use for queued or asynchronous jobs; give the client a way to check the status. |
| 203 | Non-Authoritative Information | The returned metadata comes from a copy, not the origin server. | Seen with some transforming proxies. |
| 204 | No Content | Success, with no response body. | Common for DELETE and for PUT or PATCH that return nothing. Don’t send a body. |
| 205 | Reset Content | Success; the client should reset the form or view that sent the request. | Rarely used. |
| 206 | Partial Content | Only part of the resource is returned, as asked by a Range header. | Used for resumable downloads and video seeking. |
| 207 | Multi-Status | WebDAV: the body contains separate statuses for several resources. | Used by WebDAV and some batch APIs. |
| 208 | Already Reported | WebDAV: members of a binding were already listed earlier. | Rare. |
| 226 | IM Used | The response is the result of instance manipulations (delta encoding). | Rare. |
| 300 | Multiple Choices | There are several possible representations; the client should choose. | Rarely used in practice. |
| 301 | Moved Permanently | The resource has a new permanent URL, given in Location. | Search engines move ranking to the new URL. Browsers may change POST to GET; use 308 to keep the method. |
| 302 | Found | The resource is temporarily at another URL, given in Location. | Browsers usually follow with GET. Use 307 to keep the method. |
| 303 | See Other | Get the result from another URL with GET. | Use after a form POST to redirect to a result page (Post/Redirect/Get). |
| 304 | Not Modified | The cached copy is still valid; no body is sent. | Response to a conditional request with If-None-Match or If-Modified-Since. |
| 307 | Temporary Redirect | Temporarily at another URL; repeat the request there with the same method and body. | The method-preserving version of 302. |
| 308 | Permanent Redirect | Permanently at another URL; repeat the request with the same method and body. | The method-preserving version of 301. |
| 400 | Bad Request | The server can’t process the request because it’s malformed. | Invalid JSON, missing required fields, or bad parameters. Return details of what’s wrong. |
| 401 | Unauthorized | Authentication is required or failed. | Missing, expired or invalid credentials. Send a WWW-Authenticate header. (It really means “unauthenticated”.) |
| 402 | Payment Required | Reserved for payment; some APIs use it when a plan limit or bill is unpaid. | Check your billing or plan. |
| 403 | Forbidden | The server understood who you are but refuses the request. | The user lacks permission. Logging in again won’t help, unlike 401. |
| 404 | Not Found | No resource exists at this URL. | Wrong path or ID, or a deleted resource. Also used to hide resources from unauthorised users. |
| 405 | Method Not Allowed | The URL exists but doesn’t support this HTTP method. | For example, POST to a read-only endpoint. Include an Allow header listing valid methods. |
| 406 | Not Acceptable | No representation matches the Accept headers. | The client asked for a format the server can’t produce. |
| 407 | Proxy Authentication Required | Like 401, but for a proxy between client and server. | Configure proxy credentials. |
| 408 | Request Timeout | The server gave up waiting for the client to finish sending the request. | Slow or stalled uploads. Safe to retry. |
| 409 | Conflict | The request conflicts with the current state of the resource. | Duplicate unique values, edit conflicts, or invalid state transitions. |
| 410 | Gone | The resource existed but was permanently removed. | Tells clients and search engines to stop asking. |
| 411 | Length Required | The server requires a Content-Length header. | Send the body length, or use chunked encoding if allowed. |
| 412 | Precondition Failed | A condition in the request headers, such as If-Match, was false. | Used for optimistic concurrency: someone else changed the resource first. |
| 413 | Content Too Large | The request body is larger than the server accepts. | Upload limits in the app, nginx (client_max_body_size) or a load balancer. |
| 414 | URI Too Long | The URL is longer than the server accepts. | Move large parameters from the query string into a POST body. |
| 415 | Unsupported Media Type | The server doesn’t accept the request body’s format. | Usually a missing or wrong Content-Type, such as sending JSON without application/json. |
| 416 | Range Not Satisfiable | The requested byte range is outside the resource. | The client asked for bytes beyond the end of the file. |
| 417 | Expectation Failed | The server can’t meet the Expect header. | Rare; usually about Expect: 100-continue. |
| 418 | I'm a teapot | An April Fools’ joke from RFC 2324; the server refuses to brew coffee. | Some APIs use it for blocked or joke requests. |
| 421 | Misdirected Request | The request reached a server that can’t answer for that host. | Seen with HTTP/2 connection reuse across hostnames that share a certificate. |
| 422 | Unprocessable Content | The body is well-formed but has semantic errors. | Validation failures: the JSON parses, but values are invalid. Popular in REST APIs. |
| 423 | Locked | WebDAV: the resource is locked. | Wait for the lock to be released. |
| 424 | Failed Dependency | WebDAV: failed because a previous request failed. | Rare. |
| 425 | Too Early | The server won’t risk processing a request that might be replayed. | Related to TLS 1.3 early data (0-RTT). |
| 426 | Upgrade Required | The client must switch to another protocol, named in the Upgrade header. | For example, a newer TLS or HTTP version. |
| 428 | Precondition Required | The server requires a conditional request, such as If-Match. | Prevents lost updates; fetch the ETag first. |
| 429 | Too Many Requests | The client sent too many requests in a given time (rate limiting). | Slow down and retry after the Retry-After header; use exponential backoff. |
| 431 | Request Header Fields Too Large | The headers, or one header, are too large. | Often oversized cookies. Clear cookies or reduce header size. |
| 451 | Unavailable For Legal Reasons | The resource can’t be provided for legal reasons, such as a court order. | Named after Fahrenheit 451. |
| 500 | Internal Server Error | An unexpected error happened on the server. | A bug or unhandled exception. Check the server logs; never expose stack traces to clients. |
| 501 | Not Implemented | The server doesn’t support the functionality required. | Usually an unrecognised HTTP method. |
| 502 | Bad Gateway | A gateway or proxy got an invalid response from the upstream server. | The app behind nginx, a load balancer or a CDN crashed, refused the connection or sent garbage. |
| 503 | Service Unavailable | The server is temporarily unable to handle the request. | Overload or maintenance. Send Retry-After. Free hosting tiers return it while waking up. |
| 504 | Gateway Timeout | A gateway or proxy didn’t get a response from upstream in time. | The app is too slow or hung. Check slow queries and upstream timeouts. |
| 505 | HTTP Version Not Supported | The server doesn’t support the HTTP version used. | Rare. |
| 506 | Variant Also Negotiates | A content-negotiation configuration error on the server. | Rare. |
| 507 | Insufficient Storage | WebDAV: the server can’t store what’s needed to complete the request. | Out of disk space or quota. |
| 508 | Loop Detected | WebDAV: the server found an infinite loop while processing. | Rare. |
| 510 | Not Extended | Further extensions are required to fulfil the request. | Obsolete. |
| 511 | Network Authentication Required | The client must sign in to the network, like Wi-Fi captive portals. | Open a browser to complete the portal login. |