The client should continue with its request by sending the remainder of the request. This interim response is used to inform the client that the initial part of the request has been received and has not yet been rejected by the server.
The client request has asked the server to switch protocols and the server is acknowledging that it will do so and comply with the client's request.
This server response means that the request is successful and the requested information is returned to the client.
The request has been fulfilled, resulting in the creation of a new resource
Indicates multiple options for the resource from which the client may choose. For example, this code could be used to present multiple video format options, to list files with different filename extensions.
The server responds with a 302 error message when the requested resource has been temporarily moved to a different URL. Usually the server response contains a reference to the new URL where the resource was moved. Clients should continue to use the request URL since the redirection might be altered on occasion.
Indicates that the resource has not been modified since the version specified by the request headers If-Modified-Since or If-None-Match. In such case, there is no need to retransmit the resource since the client still has a previously-downloaded copy
The 306 status code was used in a previous version of the specification, but is no longer used and currently the code is reserved.
With this response a web server informs the client that all future requests should be sent using a different URI.
The server responds with a 301 error message when the requested resource has been assigned a new permanent URL.
The response to the request can be found under another URI using the GET method. When received in response to a POST (or PUT/DELETE), the client should presume that the server has received the data and should issue a new GET request to the given URI
The requested resource is available only through a proxy, the address for which is provided in the response.
With this response a web server informs the client that the requested URL resides temporarily under a different URL. The new temporary URL should be given in the response from the server. The recipient is expected to follow the redirection but future requests can still be directed to the original URL.
This group of HTTP status codes indicates that the request for the resource contains bad syntax or cannot be filled for some other reason, presumably by fault of the client sending the request. Except when responding to a HEAD request, the server SHOULD include an explanation of the error situation and whether it is a temporary or permanent condition.
The server cannot or will not process the request due to an apparent client error (e.g., malformed request syntax, size too large, invalid request message framing, or deceptive request routing).
This code is reserved for future use. It was intended the 402 code to be used as part of some form of digital payment, but that has not happened.
The requested resource could not be found but may be available in the future. Subsequent requests by the client are permissible.
The requested resource is capable of generating only content not acceptable according to the Accept headers sent in the request.
The server timed out waiting for the request. According to HTTP specifications: "The client did not produce a request within the time that the server was prepared to wait. The client MAY repeat the request without modifications at any later time.
The web server responds with this error when the requested resource is no longer available at the server, will not be available again and no forwarding address is known. This error is similar to 404, but 410 is permanent.
The server does not meet one of the preconditions that the requester put on the request.
The URI provided was too long for the server to process. Often the result of too much data being encoded as a query-string of a GET request, in which case it should be converted to a POST request. Called "Request-URI Too Long" previously.
The client has asked for a portion of the file (byte serving), but the server cannot supply that portion. For example, if the client asked for a part of the file that lies beyond the end of the file.Called "Requested Range Not Satisfiable" previously.
he request was well-formed but was unable to be followed due to semantic errors.
The request failed because it depended on another request and that request failed
This error message means User authentication is required by the responding server or that authorization has been refused for the provided credentials with the request.
The request sent to the server was a legal request, the server understood it but is refusing to respond to it and to process it. Authorization will not help in this case.
A request method is not supported for the requested resource; for example, a GET request on a form that requires data to be presented via POST, or a PUT request on a read-only resource.
This error code is similar to 401 (Unauthorized) and the server responds with 407 error when the request from the client (web browser or our monitoring agent) was correct, but access to the URL resource requires that the client must first authenticate itself with the proxy.
Indicates that the request could not be processed because of conflict in the request, such as an edit conflict between multiple simultaneous updates.
This error code means that the server refuses to accept the request without a defined content-length. The client should repeat the request adding a valid content-length header field containing the length of the message body in the request message.
The server is refusing to process a request because the request entity is larger than the server is willing or able to process. The server may close the connection to prevent the client from continuing the request.
The server is refusing to service the request because the entity of the request is in a format not supported by the requested resource for the requested method.
The web server responds with this status code when the expectation given in an Expect request-header field could not be fulfilled by this server, or, if the server is a proxy and has clear evidence that the request could not be fulfilled by the next-hop server.
The resource that is being accessed is locked.
This group of HTTP status codes indicates that the server is aware that it is on error or is incapable of performing the request. The server response usually includes an explanation of the error situation and if it is a temporary or permanent condition. These response codes in this group are applicable to any request method.
A generic error message, given when an unexpected condition was encountered and no more specific message is suitable.
The server was acting as a gateway or proxy and received an invalid response from the upstream server.
The server was acting as a gateway or proxy and did not receive a timely response from the upstream server.
Transparent content negotiation for the request results in a circular reference.
The server detected an infinite loop while processing the request).
The server either does not recognize the request method, or it lacks the ability to fulfil the request. Usually this implies future availability (e.g., a new feature of a web-service API).
The server is currently unavailable (because it is overloaded or down for maintenance). Generally, this is a temporary state.
The server does not support the HTTP protocol version used in the request.
The server is unable to store the representation needed to complete the request.
Further extensions to the request are required for the server to fulfil it.