HTTP Status Codes Reference
Complete reference guide for HTTP response status codes used in web development
Status Codes Reference
Find detailed information about HTTP response codes, reason phrases, and their meanings
| Status | Reason Phrase | Meaning | HTTP Version |
|---|---|---|---|
| Informational responses | |||
| 100 | Continue | The server has received the initial part of the request and the client should continue. | HTTP/1.1 |
| 101 | Switching Protocols | The server agrees to switch protocols as requested via the Upgrade header. | HTTP/1.1 |
| Successful responses | |||
| 200 | OK | Request succeeded. For GET, the resource is returned; for HEAD, headers only; for POST, the result of the action. | HTTP/0.9+ |
| 201 | Created | The request succeeded and a new resource was created. | HTTP/0.9+ |
| 202 | Accepted | The request has been accepted for processing, but the processing has not been completed. | HTTP/0.9+ |
| 203 | Non-Authoritative Information | Returned metadata is from a local or third-party copy, not the origin server. | HTTP/0.9, 1.1 |
| 204 | No Content | No content to send for this request, but headers may be useful (e.g., cache updates). | HTTP/0.9+ |
| 205 | Reset Content | Tells the user agent to reset the document which sent the request. | HTTP/1.1 |
| 206 | Partial Content | Used when serving partial content via the Range header. | HTTP/1.1 |
| Redirection | |||
| 300 | Multiple Choices | The request has more than one possible response; the user agent or user should choose one. | HTTP/1.0+ |
| 301 | Moved Permanently | The resource has a new permanent URI in the Location header. | HTTP/0.9+ |
| 302 | Found | The resource is temporarily located at a different URI (see Location). | HTTP/0.9+ |
| 303 | See Other | Directs the client to retrieve the resource with a GET from another URI. | HTTP/0.9, 1.1 |
| 304 | Not Modified | The resource has not been modified; use a cached version. | HTTP/0.9+ |
| 305 | Use Proxy | The requested resource must be accessed through the proxy given by the Location field. | HTTP/1.1 |
| 306 | Unused | This status code is no longer used (reserved). | HTTP/1.1 |
| 307 | Temporary Redirect | Temporarily redirects to the URI in Location using the same request method. | HTTP/1.1 |
| 308 | Permanent Redirect | Permanently redirects to the URI in Location using the same request method. | HTTPbis (draft) |
| Client errors | |||
| 400 | Bad Request | The server cannot process the request due to a client error (e.g., malformed syntax). | HTTP/0.9+ |
| 401 | Unauthorized | Authentication is required to access the resource. | HTTP/0.9+ |
| 402 | Payment Required | Reserved for future use. | HTTP/0.9, 1.1 |
| 403 | Forbidden | The client does not have access rights to the content. | HTTP/0.9+ |
| 404 | Not Found | The server cannot find the requested resource. | HTTP/0.9+ |
| 405 | Method Not Allowed | The request method is known by the server but is not supported for the target resource. | HTTP/1.1 |
| 406 | Not Acceptable | No acceptable representation could be found following content negotiation. | HTTP/1.1 |
| 407 | Proxy Authentication Required | Authentication with a proxy is required. | HTTP/1.1 |
| 408 | Request Timeout | The server timed out waiting for the request. | HTTP/1.1 |
| 409 | Conflict | The request conflicts with current state of the resource. | HTTP/1.1 |
| 410 | Gone | The resource is permanently removed and no forwarding address is known. | HTTP/1.1 |
| 411 | Length Required | The request did not specify the length of its content, which is required. | HTTP/1.1 |
| 412 | Precondition Failed | One or more preconditions given in the request header fields were evaluated as false. | HTTP/1.1 |
| 413 | Payload Too Large | The request entity is larger than the server is willing or able to process. | HTTP/1.1 |
| 414 | URI Too Long | The URI provided was too long for the server to process. | HTTP/1.1 |
| 415 | Unsupported Media Type | The request entity has a media type which the server or resource does not support. | HTTP/1.1 |
| 416 | Range Not Satisfiable | The requested range cannot be satisfied; the range may be outside the size of the target resource. | HTTP/1.1 |
| 417 | Expectation Failed | The expectation given in the request's Expect header could not be met. | HTTP/1.1 |
| 418 | I'm a teapot | Defined by RFC 2324 as an April Fools' joke (HTCPCP). | HTCPCP |
| Server errors | |||
| 500 | Internal Server Error | The server encountered an unexpected condition that prevented it from fulfilling the request. | HTTP/0.9+ |
| 501 | Not Implemented | The request method is not supported by the server and cannot be handled. | HTTP/0.9+ |
| 502 | Bad Gateway | The server, while acting as a gateway or proxy, received an invalid response from the upstream server. | HTTP/0.9+ |
| 503 | Service Unavailable | The server is not ready to handle the request (maintenance or overload). May include Retry-After. | HTTP/0.9+ |
| 504 | Gateway Timeout | The server, while acting as a gateway or proxy, did not receive a timely response from the upstream server. | HTTP/1.1 |
| 505 | HTTP Version Not Supported | The HTTP version used in the request is not supported by the server. | HTTP/1.1 |