200 OK

The 200 OK status code indicates that the request has succeeded. The payload sent in a 200 response depends on the request method. For the methods defined by this specification, the intended meaning of the payload can be summarized as[1]:

  • GET a representation of the target resource[2];
  • HEAD the same representation as GET, but without the representation data[3];
  • POST a representation of the status of, or results obtained from, the action[4];
  • PUT, DELETE a representation of the status of the action[5];
  • OPTIONS a representation of the communications options[6];
  • TRACE a representation of the request message as received by the end server[7].

Aside from responses to CONNECT, a 200 response always has a payload, though an origin server MAY generate a payload body of zero length. If no payload is desired, an origin server ought to send 204 (No Content) instead. For CONNECT, no payload is allowed because the successful result is a tunnel, which begins immediately after the 200 response header section[8].

A 200 response is cacheable by default; i.e., unless otherwise indicated by the method definition or explicit cache controls[9][10].


We like to give credit where credit is due. This article contains 2 references with a total of 10 citations.

  1. [1] [2] [3] [4] [5] [6] [7] [8] [10] Fielding, Roy T, And Julian F Reschke. "6.3.1. 200 OK." HTTP/1.1 Semantics and Content, IETF Trust, 1 Jun. 2014, tools.ietf.org/html/rfc7231#section-6.3.1

  2. [9] Fielding, Roy T, And Julian F Reschke. "4.2.2. Calculating Heuristic Freshness." HTTP/1.1 Caching, IETF Trust, 1 Jun. 2014, tools.ietf.org/html/rfc7234#section-4.2.2

Notify me about new features:

upcoming free account access, charts & stats, historical data, API, etc.

* All fields required.