HTTP Status Codes 2xx

200 OK - The request sent by the client has succeeded. With this response server returns the requested information according to the request sent by the client. Always server returns a 200 status code with some extra data according to the request method. This means the request was successfull and this is the data as per the request. i.e. server was able to find the requested resource or was able to perform the requested action and in a position to deliver that to the client.

For a GET request server returns the requested resource. For example if the client requested a html file then server returns the file with this code. For a graphic file or other type of resources server returns that resource with the 200 response.

For a HEAD request server returns the header info of the requested resource. For example for a html file, server returns the http header part of the file. This normally includes the HTTP version, date, Server info, last modified date, etag, conent-type, content-length, conent-style-type etc. Some search engine spiders like Googlebot uses head requests to get quick info of a file.

For a POST request server returns the result of that action. For example when you submit a HTML form with post request, server takes that values from the from elements like input, textarea, select and return to the client with 200 status code.

201 Created - This response means the request was succeffully completed and a new resource has been created. In the entity of the response newly created URIs (Uniform Resource Identifier) will be listed with the most specific URI in the location header field. The entity type will be described in the Content-Type header field. 201 status code also may return an etag for the newly created resoruce.

202 Accepted - This means that server accepted the request but processing not completed. The request was accepted by the server for processing but it might be processed or disallowed at the actual time of processing. Since http communication is asynchronous there is no way to return a status code at the time of processing. When the server actually run the task the connection to the client may not exists. So the server just send a 202 telling the client that it accepted the request and will consider later for processing. There is no guarantee that it will be processed. But it will return the current status of the request or an approximate time user can expect the process to complete. This type of response is useful for routine jobs or tasks run once a day or run once in a predefined time.

203 Non-Authoritative Information - The meta information returned in the entity header is not definitive set as available in the origin server.

204 No Content - The server completed the request successfuly but does not require the return of an entity-body. It might return an updated meta information like headers.

205 Reset Content - The request was successful but the User-Agent should reset the document view that caused the request.

206 Partial Content - The partial GET request has been successful.