200 OK
The request succeeded. What the body contains depends on the method used.
| Class | Success (2xx) |
|---|---|
| Defined in | RFC9110, Section 15.3.1 |
| Cacheable by default | Yes (RFC 9110, section 15.1) |
Common causes
- A GET returned the resource, or a POST/PUT completed and returned a result.
- The request passed every check on the server.
What to do
Nothing to fix. If the content is wrong, look at the application logic, since 200 only says the request was handled.
Related codes
- 201 Created: The request succeeded and created a new resource, usually identified by a Location header.
- 204 No Content: The request succeeded and there is no body to send back.
- 304 Not Modified: The cached copy is still valid, so no body is sent.