Open topic with navigation
The World Wide Web Consortium developed a set of standard Status Codes for understanding the results of a request. The codes are 3-digit integers, where the first digit represents the class, and the second two digits give you more information about the response within that class.
Note: Status Code Classes, Status Codes, Labels, and Descriptions are defined by the World Wide Web Consortium: please refer to http://www.w3.org/Protocols for the full current definition. The information provided here is for your convenience only.
There are 5 general classes for the response status.
|1XX Series||Information||The request was received, continuing process.|
|2XX Series||Successful||The request was successfully received, understood, and accepted.|
|3XX Series||Redirection||Further action needs to be taken in order to complete the request.|
|4XX Series||Client Error||The request contains incorrect syntax or cannot be fulfilled.|
|5XX Series||Server Error||The server failed to fulfill an apparently valid request.|
Information status codes are provisional responses from the web server. This is an interim status, notifying the client that the response has been received, and further action will be taken.
|100||Continue||The initial part of a request has been received. The server intends to send a final response after the request has been fully received and acted upon.|
|101||Switching Protocols||The server must generate an Upgrade header field in the response that indicates which protocol it will be switched to.|
The Successful status codes indicate that the request was received, understood, and successful.
|200||OK||Request has succeeded.|
|201||Created||Request was fulfilled and resulted in new resources being created.|
|202||Accepted||Request has been accepted for processing, but processing has not completed.|
|203||Non-authoritative information||Request was successful but the enclosed payload has been modified from the origin server’s 200 response.|
|204||No Content||Request successfully fulfilled, and no additional content to send in the response payload body.|
|205||Reset Content||Request fulfilled, and the server wants the user agent to reset the “document view”.|
Further action needs to be taken in order to fulfill the request. The agent MAY automatically redirect.
|300||Multiple Choices||Target resource has more than one representation, each with it’s own identifier, and information about the alternatives is being provided.|
|301||Moved Permanently||The target resource was assigned a new permanent URI, and future references to this resource should use one of the enclosed URIs.|
|302||Found||Target resource resides temporarily under a different URI.|
|303||See Other||Server is redirecting the user agent to a different resource, as indicated by the URI in the header field.|
|305||Use Proxy||No longer used.|
|307||Temporary Redirect||The target resource resides temporarily under a different URI and the user agent must not change the request method if it performs an automatic redirection to that URI.|
The client appears to have provided something in error.
|400||Bad Request||The server cannot or will not process the request due to something which is perceived to be a client error.|
|402||Payment Required||Reserved for future use.|
|403||Forbidden||The server understood the request but refuses to authorize it.|
|404||Not Found||The origin server did not find a current representation for the target resource or is not willing to disclose that one exists.|
|405||Method Not Allowed||The method received in the request-line is known by the origin server but not supported by the target resource.|
|406||Not Acceptable||The target resource does not have a current representation that would be acceptable to the user agent.|
|407||Proxy Authentication Required|
|408||Request Time-Out||The server did not receive a complete request message within the time that it was prepared to wait.|
|409||Conflict||The request could not be completed due to a conflict with the current state of the target resource.|
|410||Gone||The target resource is no longer available at the origin server, and this is likely to be permanent.|
|411||Length Required||The server refuses to accept the request without a defined Content-Length.|
|413||Payload Too Large||The server is refusing to process a request because the request payload is larger than the server is willing or able to process.|
|414||URI Too Long||The server is refusing to service the request because the request-target is longer than the server is willing to interpret.|
|415||Unsupported Media Type||The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.|
|416||Range Not Satisfiable|
|417||Expectation Failed||The expectation given in the request’s Expect header field could not be met by at least one of the inbound servers.|
|426||Upgrade Required||The server refuses to perform the request using the current protocol, but might be willing to do so after the client upgrades to a different protocol.|
The server is aware that it has erred or is incapable of performing the request.
|500||Internal Server Error||The server encountered an unexpected condition that prevented it from fulfilling the request.|
|501||Not Implemented||The server does not support the functionality required to fulfill the request.|
|502||Bad Gateway||While acting as a gateway or proxy, the server received an invalid response from an inbound server accessed while attempting to fulfill the request.|
|503||Service Unavailable||The server is currently unable to handle the request due to a temporary overload or scheduled maintenance, which will likely be alleviated after some delay.|
|504||Gateway Time-Out||While acting as a gateway or proxy, the server did not receive a timely response from an upstream server it needed to access in order to complete the request.|
|505||HTTP Version Not Supported||The server does not support or refuses to support the major version of HTTP used in the request message.|
W3C: HTTP - Hypertext Transfer Protocol (February 06, 2014, Draft -26), HTTP/1.1, part 2: Semantics and Content (http://www.w3.org/protocols).