||Standard response for successful HTTP requests. The actual response will depend on the request method used. In a GET request, the response will contain an entity corresponding to the requested resource. In a POST request the response will contain an entity describing or containing the result of the action.
||The request has been fulfilled and resulted in a new resource being created.
||The request has been accepted for processing, but the processing has not been completed. The request might or might not eventually be acted upon, as it might be disallowed when processing actually takes place.
||Non-Authoritative Information (since HTTP/1.1)
||The server successfully processed the request, but is returning information that may be from another source.
||The server successfully processed the request, but is not returning any content. Usually used as a response to a successful delete request.
||The server successfully processed the request, but is not returning any content. Unlike a 204 response, this response requires that the requester reset the document view.
||The server is delivering only part of the resource due to a range header sent by the client. The range header is used by tools like wget to enable resuming of interrupted downloads, or split a download into multiple simultaneous streams.
||Multi-Status (WebDAV; RFC 4918)
||The message body that follows is an XML message and can contain a number of separate response codes, depending on how many sub-requests were made.
||Already Reported (WebDAV; RFC 5842)
||The members of a DAV binding have already been enumerated in a previous reply to this request, and are not being included again.
||IM Used (RFC 3229)
||The server has fulfilled a GET request for the resource, and the response is a representation of the result of one or more instance-manipulations applied to the current instance.