<Dd> Used to return some response headers before final HTTP message . </Dd> <P> This class of status codes indicates the action requested by the client was received, understood and accepted . </P> <Dl> <Dt> 200 OK </Dt> <Dd> 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 . </Dd> <Dt> 201 Created </Dt> <Dd> The request has been fulfilled, resulting in the creation of a new resource . </Dd> <Dt> 202 Accepted </Dt> <Dd> The request has been accepted for processing, but the processing has not been completed . The request might or might not be eventually acted upon, and may be disallowed when processing occurs . </Dd> <Dt> 203 Non-Authoritative Information (since HTTP / 1.1) </Dt> <Dd> The server is a transforming proxy (e.g. a Web accelerator) that received a 200 OK from its origin, but is returning a modified version of the origin's response . </Dd> <Dt> 204 No Content </Dt> <Dd> The server successfully processed the request and is not returning any content . </Dd> <Dt> 205 Reset Content </Dt> <Dd> 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 . </Dd> <Dt> 206 Partial Content (RFC 7233) </Dt> <Dd> The server is delivering only part of the resource (byte serving) due to a range header sent by the client . The range header is used by HTTP clients to enable resuming of interrupted downloads, or split a download into multiple simultaneous streams . </Dd> <Dt> 207 Multi-Status (WebDAV; RFC 4918) </Dt> <Dd> The message body that follows is by default an XML message and can contain a number of separate response codes, depending on how many sub-requests were made . </Dd> <Dt> 208 Already Reported (WebDAV; RFC 5842) </Dt> <Dd> The members of a DAV binding have already been enumerated in a preceding part of the (multistatus) response, and are not being included again . </Dd> <Dt> 226 IM Used (RFC 3229) </Dt> <Dd> The server has fulfilled a request for the resource, and the response is a representation of the result of one or more instance - manipulations applied to the current instance . </Dd> </Dl> <Dd> 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 . </Dd>

What is the success response for get request
find me the text answering this question