200 OK

200 OK reports success, with response content defined in relation to the request method.

  • status codes
  • success

Meaning

200 OK means the request succeeded. The meaning of response content depends on the request method: for GET it is a representation of the target, while for POST it is the status or result of the action.

HTTP/1.1 200 OK
Content-Type: application/json

{"status":"ready"}

Expected result: the HTTP request succeeded and the response contains JSON. Whether ready is an application success state depends on the application’s own contract.

Method-specific constraints

A response to HEAD never includes content even when its status is 200. A successful CONNECT switches to tunnel mode instead of carrying ordinary response content.

Caching

200 responses are heuristically cacheable unless method semantics or explicit cache controls say otherwise. Cacheability does not mean that a particular cache stored or reused the response.

Primary sources