HTTP Status Codes
Every common HTTP status code, with what it means — searchable, in your browser.
41 of 41
| Code | Name | Description |
|---|---|---|
| 100 | Continue | The server has received the request headers and the client should proceed to send the request body. |
| 101 | Switching Protocols | The server is switching protocols as requested by the client via the Upgrade header. |
| 102 | Processing | The server has received and is processing the request, but no response is available yet (WebDAV). |
| 103 | Early Hints | Used to return some response headers before the final HTTP message, often to preload resources. |
| 200 | OK | The request succeeded. The meaning depends on the method (GET returns the resource, POST returns the result). |
| 201 | Created | The request succeeded and a new resource was created, typically after a POST or PUT. |
| 202 | Accepted | The request has been accepted for processing, but the processing has not been completed. |
| 203 | Non-Authoritative Information | The returned metadata is from a local or third-party copy, not the origin server. |
| 204 | No Content | The request succeeded but there is no content to send in the response body. |
| 205 | Reset Content | Tells the client to reset the document view that sent the request, e.g. clear a form. |
| 206 | Partial Content | The server is delivering only part of the resource due to a Range header sent by the client. |
| 300 | Multiple Choices | The request has more than one possible response; the client should choose one of them. |
| 301 | Moved Permanently | The resource has been permanently moved to a new URL given in the Location header. |
| 302 | Found | The resource resides temporarily under a different URL given in the Location header. |
| 303 | See Other | The response can be found under another URL using a GET method, often after a POST. |
| 304 | Not Modified | The cached version of the resource is still valid; the client can reuse it. |
| 307 | Temporary Redirect | The resource is temporarily at a different URL and the original method must be reused. |
| 308 | Permanent Redirect | The resource is permanently at a different URL and the original method must be reused. |
| 400 | Bad Request | The server cannot process the request due to a client error such as malformed syntax. |
| 401 | Unauthorized | Authentication is required and has either failed or not yet been provided. |
| 402 | Payment Required | Reserved for future use; sometimes used by APIs that require payment or a paid plan. |
| 403 | Forbidden | The server understood the request but refuses to authorize it; access is not allowed. |
| 404 | Not Found | The server cannot find the requested resource; the URL is not recognized. |
| 405 | Method Not Allowed | The request method is known but not supported for the target resource. |
| 406 | Not Acceptable | The resource cannot produce a response matching the Accept headers sent by the client. |
| 408 | Request Timeout | The server timed out waiting for the request; the client took too long to send it. |
| 409 | Conflict | The request conflicts with the current state of the target resource, e.g. an edit conflict. |
| 410 | Gone | The resource is permanently gone and no forwarding address is known. |
| 411 | Length Required | The server requires a Content-Length header, which the request did not provide. |
| 413 | Payload Too Large | The request body is larger than the server is willing or able to process. |
| 414 | URI Too Long | The requested URI is longer than the server is willing to interpret. |
| 415 | Unsupported Media Type | The request body is in a format the server does not support. |
| 418 | I'm a Teapot | An April Fools' joke from RFC 2324; the server refuses to brew coffee in a teapot. |
| 422 | Unprocessable Entity | The request was well-formed but contains semantic errors that prevent processing (WebDAV). |
| 429 | Too Many Requests | The client has sent too many requests in a given amount of time (rate limiting). |
| 500 | Internal Server Error | The server encountered an unexpected condition that prevented it from fulfilling the request. |
| 501 | Not Implemented | The server does not recognize the request method or lacks the ability to fulfill it. |
| 502 | Bad Gateway | The server, acting as a gateway, received an invalid response from an upstream server. |
| 503 | Service Unavailable | The server is not ready to handle the request, often due to maintenance or overload. |
| 504 | Gateway Timeout | The server, acting as a gateway, did not get a timely response from an upstream server. |
| 505 | HTTP Version Not Supported | The server does not support the HTTP protocol version used in the request. |
How to read an HTTP status code
The first digit groups the response: 1xx is informational, 2xx means success, 3xx is a redirect, 4xx is a client error (your request was wrong), and 5xx is a server error (the server failed). Type a code or a keyword like ‘redirect’ to filter the table.
Questions
What does a 404 status code mean?
404 Not Found means the server could not find the requested resource — the URL does not point to anything the server recognizes. It is a client-side error in the 4xx range.
What is the difference between 401 and 403?
401 Unauthorized means you are not authenticated — you need to log in. 403 Forbidden means you are authenticated but not allowed to access the resource.
What does a 500 status code mean?
500 Internal Server Error is a generic server-side failure. The server hit an unexpected condition and could not complete the request; the problem is on the server, not your request.