Mirrors/httpstatuses
1
0
Fork 0
mirror of https://github.com/rmaake1/httpstatuses.git synced 2024-09-04 16:49:45 +02:00
Code Issues Packages Projects Releases Wiki Activity
d8a693bf27
httpstatuses/contents/codes/200.md
Samuel Ryan d8a693bf27 Remove markdown line limit (#52) 
* Removes line length limit from Status Code Markdown

This will make the data easier to use when we develop the API, it needs
to be consistent, arbitrary new lines (especially in text format) will
be a major issue, so some sort of workaround would have to be
implemented, easier to simply fix the source files.

* Removes line length limit from misc. Markdown files
2016-04-23 01:12:07 +01:00

1.6 KiB
Raw Blame History

set code title references
2 200 OK
Rails HTTP Status Symbol Go HTTP Status Constant Symfony HTTP Status Constant
:ok http.StatusOK Response::HTTP_OK

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:

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

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.

A 200 response is cacheable by default; i.e., unless otherwise indicated by the method definition or explicit cache controls1.