| Previous | Next |
| HTTP_EARLY_HINTS | HTTP_STATUS_CREATED |
HTTP_STATUS_OK
For GET, a 200 response normally carries a representation of the requested resource. For POST, it commonly represents the result of the submitted action; for HEAD, headers describe the response without a message body.
A 200 response is cacheable by default unless cache controls or the request method say otherwise. When a newly created resource should be identified explicitly, a server generally uses 201 instead.
Operational meaning of HTTP 200 for HTTP_STATUS_OK
HTTP 200 (this result) is a successful response. AllStat records its meaning as “200 OK”. Interpret it with the request method, selected representation, response headers, and the specification or product that defines the code; the number alone does not prove that application work completed.
Client and server handling
- Verify what work the response representation says was completed; this result can still describe asynchronous or partial handling.
- use validators, location/status links, and application identifiers supplied by the server.
- do not retry a non-idempotent request merely because the client did not understand the response body.
For telemetry, record HTTP 200, method, authority, route template rather than secrets, response headers relevant to caching or retry, latency, upstream identity, and whether the response originated at the application or an intermediary.
Looking for a different code? Search another status or error code.