The request has succeeded.


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

A 200 response is cacheable by default; unless otherwise indicated by the method definition or explicit cache controls.


The HTTP 200 OK success status response code indicates that the request has succeeded. A 200 response is cacheable by default.

The meaning of a success depends on the HTTP request method:

The successful result of a PUT or a DELETE is often not a 200 OK but a 204 No Content (or a 201 Created when the resource is uploaded for the first time).


Further Reading


200 OK | The HTTP Working Group

200 OK

MDN web docs

GET method

MDN web docs

HEAD method

MDN web docs

POST method

MDN web docs

TRACE method

MDN web docs

PUT method

MDN web docs

DELETE method

MDN web docs

CONNECT method

MDN web docs