The 2xx class means the request was successfully received, understood, and accepted.
Table of 2xx Codes
| Code | Name | Summary |
|---|---|---|
| 200 | OK | Standard success. |
| 201 | Created | New resource created; Location may be set. |
| 202 | Accepted | Processing deferred; result not yet available. |
| 203 | Non-Authoritative Information | Metadata altered by a proxy. |
| 204 | No Content | Success, no body. |
| 205 | Reset Content | Client should reset the document view. |
| 206 | Partial Content | Range response. |
| 207 | Multi-Status | WebDAV multi-result. |
| 208 | Already Reported | WebDAV deduplication of results. |
| 226 | IM Used | Instance-manipulations applied. |
200 OK
General success.
Caching: Cacheable by default for GET if headers permit. Pair with validators (ETag, Last-Modified) for efficient 304.
201 Created
Return when a resource is created; include Location: with the canonical URI.
Pattern: POST-to-collection → 201 + representation.
202 Accepted
Async pattern: request queued. Provide a status endpoint or webhook contract.
203 Non-Authoritative Information
Proxy-transformed metadata. Rare on modern sites.
204 No Content
No body. Common for DELETE, idempotent PUT, or OPTIONS preflight success.
205 Reset Content
Client should reset UI state. Seldom used.
206 Partial Content
Response to a Range: request. Include Content-Range and correct Content-Length.
CDN note: Enable range coalescing and ensure origin supports byte ranges for large media.
207 / 208 / 226
WebDAV/IM features. Typically internal to enterprise file services.