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: A 200 response is heuristically cacheable unless the method or explicit cache controls prohibit it. Use available validators such as ETag and Last-Modified to support validation.
201 Created
Return when a request creates one or more resources. Location identifies the primary resource; without it, the target URI identifies that resource.
Pattern: POST to collection -> 201 with a representation.
202 Accepted
The server accepted the request, but processing is incomplete and might not occur. The response should describe current status and identify a status monitor when available.
203 Non-Authoritative Information
Proxy-transformed metadata. Rare on modern sites.
204 No Content
The action succeeded, and the response contains no content or trailers. A 204 response is heuristically cacheable unless other controls apply.
205 Reset Content
Client should reset UI state. Seldom used.
206 Partial Content
A response to a range request contains one or more parts of the selected representation. Required fields depend on whether the response contains one range or multiple ranges. CDN note: Verify range storage and combination behavior. Combining stored ranges requires the same strong validator.
207 / 208 / 226
WebDAV/IM features. Typically internal to enterprise file services.