||The request has been fulfilled and resulted in a new resource being created. The newly created resource can be referenced by the URI(s) returned in the URI-header field of the response, with the most specific URI for the resource given
by a Location header field.
||The request has been accepted for processing, but the processing has not been completed.
||The returned metainformation in the Entity-Information header is not the definitive set as available from the origin server, but is gathered from a local or a third-party copy.
||The server has fulfilled the request, but there is no new information to send back.
||The requested resource is available at one or more locations and a preferred location could not be determined via content negotiation.
||The requested resource has been assigned a new, permanent URI; any future references to this resource should be done using one of the returned URIs.
||The requested resource resides temporarily under a different URI.
||The requested resource resides under a different URI and should be accessed using a Get method on that resource.
||If the client has performed a conditional Get request and access is allowed, but the document has not been modified since the date and time specified in the If-Modified-Since field, the server responds with this status
code and does not send an Entity-Body header to the client.
||The request could not be understood by the server because it has a malformed syntax.
||The request requires user authentication. The response must include a WWW-Authenticate header field containing a challenge applicable to the requested resource.
||This code is not currently supported, but it is reserved for future use.
||The server understood the request but is refusing to perform the request because of an unspecified reason.
||The server has not found anything matching the request URI.
||Method Not Allowed
||The method specified in the request line is not allowed for the resource identified by the request URI.
||The server has found a resource matching the request URI, but not one that satisfies the conditions identified by the Accept and Accept-Encoding request headers.
|This code is reserved for future use. Itis similar to 401, but it indicates that the client first must authenticate itself with the proxy. HTTP/1.0 does not provide a means for proxy authentication.
||The client did not produce a request within the time that the server was prepared to wait.
||The request could not be completed due to a conflict with the current state of the resource.
||The requested resource is no longer available at the server, and no forwarding address is known.
|The request credentials provided by the client were rejected by the server or insufficient to grant authorization to access the resource.
|The server encountered an unexpected condition that prevented it from fulfilling the request.
||The server does not support the functionality required to fulfill the request.
||The server received an invalid response from the gateway or upstream server it accessed when attempting to fulfill the request.
|The server currently is unable to handle the request due to a temporary overloading or maintenance of the server.
||The server did not receive a timely response from the gateway or upstream server it accessed when attempting to complete the request.