AES Encryption Explained: How It Works and Why It Matters
Jun 23, 2026
10 status codes
These codes indicate that the client's request was successfully received, understood, and accepted. This is the category every developer hopes to see — everything worked as expected.
| Code | Title | Description | RFC |
|---|---|---|---|
| 200 | OK | The request has succeeded. The meaning of the success depends on the HTTP method used. | RFC 7231, Section 6.3.1 |
| 201 | Created | The request has been fulfilled and has resulted in one or more new resources being created. | RFC 7231, Section 6.3.2 |
| 202 | Accepted | The request has been accepted for processing, but the processing has not been completed. | RFC 7231, Section 6.3.3 |
| 203 | Non-Authoritative Information | The request was successful but the enclosed payload has been modified by a transforming proxy. | RFC 7231, Section 6.3.4 |
| 204 | No Content | The server has successfully fulfilled the request and there is no additional content to send. | RFC 7231, Section 6.3.5 |
| 205 | Reset Content | The server has fulfilled the request and desires that the user agent reset the document view. | RFC 7231, Section 6.3.6 |
| 206 | Partial Content | The server is delivering only part of the resource due to a range header sent by the client. | RFC 7233, Section 4.1 |
| 207 | Multi-Status | Provides status for multiple independent operations (WebDAV). | RFC 4918, Section 13 |
| 208 | Already Reported | The members of a DAV binding have already been enumerated in a preceding part of the response (WebDAV). | RFC 5842, Section 7.1 |
| 226 | IM Used | 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. | RFC 3229, Section 10.4.1 |
Blog
Jun 23, 2026
Jun 23, 2026
Jun 23, 2026
Jun 23, 2026
Jun 23, 2026
Jun 23, 2026