As a part of the HTTP (Hypertext Transfer Protocol) 0.9 specifications, the World Wide Web Consortium (W3C) established HTTP status codes in 1992. Tim Berners-Lee, who invented the web and the first web browser in 1990, defined the status codes.
The following table provides a brief overview of HTTP response status codes. The first digit of the status code specifies one of five standard classes of HTTP status responses. The message phrases shown are typical, but any human-readable alternative may be provided.
It is the responsibility of the Internet Assigned Numbers Authority (IANA) to maintain the official registry of HTTP status codes. It is also useful to note that Microsoft’s Internet Information Services (IIS) may also use additional decimal sub-codes for more specific information. These sub-codes only appear in the response payload and documentation.
If you are experiencing issues with your own company website, it may relate to the server, hosting environment, CMS (Content Management System) such as WordPress or an aspect of the website design itself.
HTTP Error Codes
| Code | Meaning | Description |
| 100 | Continue | Confirms the client about the arrival of the first part of the request and informs to continue with the rest of the request or ignore if the request has been fulfilled |
| 101 | Switching Protocols | Informs the client about the server switching the protocols to that specified in the Upgrade message header field during the current connection. |
| 103 | Checkpoint | Used in the resumable requests proposal to resume aborted PUT or POST requests. |
| 200 | OK | Standard response for successful requests |
| 201 | Created | Request fulfilled and new resource created |
| 202 | Accepted | Request accepted, but not yet processed |
| 203 | Non-Authoritative Information | Returned meta information was not the definitive set from the origin server. |
| 204 | No Content | Request succeeded without requiring the return of an entity-body |
| 205 | Reset Content | Request succeeded but require resetting of the document view that caused the request |
| 206 | Partial Content | Partial GET request was successful |
| 300 | Multiple Choices | Requested resource has multiple choices at different locations. |
| 301 | Moved Permanently | Resource permanently moved to a different URL. |
| 302 | Found | Requested resource was found under a different URL but the client should continue to use the original URL. |
| 303 | See Other | Requested response is at a different URL and can be accessed only through a GET command. |
| 304 | Not Modified | Resource not modified since the last request. |
| 305 | Use Proxy | Requested resource should be accessed through the proxy specified in the location field. |
| 306 | No Longer Used | Reserved for future use |
| 307 | Temporary Redirect | Resource has been moved temporarily to a different URL. |
| 400 | Bad Request | Syntax of the request not understood by the server. |
| 401 | Not Authorized | Request requires user authentication |
| 402 | Payment Required | Reserved for future use. |
| 403 | Forbidden | Server refuses to fulfil the request. |
| 404 | Not Found | Document or file requested by the client was not found. |
| 405 | Method Not Allowed | Method specified in the Request-Line was not allowed for the specified resource. |
| 406 | Not Acceptable | Resource requested generates response entities that has content characteristics not specified in the accept headers. |
| 407 | Proxy Authentication Required | Request requires the authentication with the proxy. |
| 408 | Request Timeout | Client fails to send a request in the time allowed by the server. |
| 409 | Conflict | Request was unsuccessful due to a conflict in the state of the resource. |
| 410 | Gone | Resource requested is no longer available with no forwarding address |
| 411 | Length Required | Server doesn’t accept the request without a valid Content-Length header field. |
| 412 | Precondition Failed | Precondition specified in the Request-Header field returns false. |
| 413 | Request Entity Too Large | Request unsuccessful as the request entity is larger than that allowed by the server |
| 414 | Request URL Too Long | Request unsuccessful as the URL specified is longer than the one, the server is willing to process. |
| 415 | Unsupported Media Type | Request unsuccessful as the entity of the request is in a format not supported by the requested resource |
| 416 | Requested Range Not Satisfiable | Request included a Range request-header field without any range-specifier value |
| 417 | Expectation Failed | Expectation given in the Expect request-header was not fulfilled by the server. |
| 420 | Method Failure (Spring Framework) | A deprecated response used by the Spring Framework when a method has failed. |
| 422 | Unprocessable Entity | Request well-formed but unable to process because of semantic errors |
| 423 | Locked | Resource accessed was locked |
| 424 | Failed Dependency | Request failed because of the failure of a previous request |
| 426 | Upgrade Required | Client should switch to Transport Layer Security |
| 440 | Login Time-out | The client’s session has expired and must log in again. |
| 49 | Retry With | The server cannot honour the request because the user has not provided the required information. |
| 450 | Blocked by Windows Parental Controls (Microsoft) | The Microsoft extension code indicated when Windows Parental Controls are turned on and are blocking access to the requested webpage. |
| 451 | Redirect | Used in Exchange ActiveSync when either a more efficient server is available or the server cannot access the users’ mailbox. The client is expected to re-run the HTTP AutoDiscover operation to find a more appropriate server. |
| 498 | Invalid Token (Esri) | Returned by ArcGIS for Server. Code 498 indicates an expired or otherwise invalid token. |
| 499 | Token Required (Esri) | Returned by ArcGIS for Server. Code 499 indicates that a token is required but was not submitted. |
| 500 | Internal Server Error | Request unsuccessful because of an unexpected condition encountered by the server. |
| 501 | Not Implemented | Request unsuccessful as the server could not support the functionality needed to fulfil the request. |
| 502 | Bad Gateway | Server received an invalid response from the upstream server while trying to fulfil the request. |
| 503 | Service Unavailable | Request unsuccessful to the server being down or overloaded. |
| 504 | Gateway Timeout | Upstream server failed to send a request in the time allowed by the server. |
| 505 | HTTP Version Not Supported | Server does not support the HTTP version specified in the request. |
| 509 | Bandwidth Limit Exceeded (Apache Web Server/cPanel) | The server has exceeded the bandwidth specified by the server administrator; this is often used by shared hosting providers to limit the bandwidth of customers. |
| 530 | Site is frozen | Used by the Pantheon web platform to indicate a site that has been frozen due to inactivity. |
| 598 | (Informal convention) Network read timeout error | Used by some HTTP proxies to signal a network read timeout behind the proxy to a client in front of the proxy. |
For information on affordable hosting solutions visit our web hosting plans.
Toby Creative – Branding & Marketing in Perth, WA is a Google Partner Agency and Local SEO Company providing website performance and improvement support services. We provide complete website design and development services as well as website hosting, CMS management and comprehensive post-launch marketing support solutions.
Contact us on 0412 622 262 or fill in our contact form to book a no obligation free initial consultation at your location so that we can discuss your specific marketing requirements.