Post

2xx - Successful response

The HTTP 200 status code signifies a successful request, indicating that the server has successfully processed the client’s request and is returning the requested resource. It represents a positive outcome in the communication between the client and the server.

Success

200 OK

It indicates that the request has succeeded and it is cacheable by default.

201 Created

To be simple, the request succeeded and a new resource was created.

202 Accepted

This indicates that the request has been accepted for processing, but the processing has not been completed; in fact, processing may not have started yet.

203 Non-Authoritative Information

The server is a transforming proxy that received a 200 OK from its origin but is returning a modified version of the origin’s response

204 No Content

The server successfully processed the client’s request, and the server is not returning any content.

205 Reset Content

The server successfully processed the client’s request, and the server asks that the client reset its document view, and that is not returning any content.

206 Partial Content

The server is delivering only part of the resource requested by the client due to a range header sent by the client.

207 - Multi-Status

Conveys information about multiple resources, for situations where multiple status codes might be appropriate.

208 - Already Reported

The members of a DAV binding have already been enumerated in a preceding part of the multi-status response, and are not being included again.

226 - IM Used

To state it simply - The server has sent the resource that was asked for.

Refererece - [Mozilla Docs Successful Responses](https://developer.mozilla.org/en-US/docs/Web/HTTP/Status#successful_responses)

Thanks for the read! Let your life be 200 OK.

- Aadarsh K

This post is licensed under CC BY 4.0 by the author.