mirror of
https://github.com/rmaake1/httpstatuses.git
synced 2024-11-02 00:32:36 +01:00
d8a693bf27
* 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
34 lines
1.6 KiB
Markdown
34 lines
1.6 KiB
Markdown
---
|
|
set: 2
|
|
code: 200
|
|
title: OK
|
|
references:
|
|
"Rails HTTP Status Symbol": ":ok"
|
|
"Go HTTP Status Constant": "http.StatusOK"
|
|
"Symfony HTTP Status Constant": "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](/204) 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 controls<sup>[1](#ref-1)</sup>.
|
|
|
|
---
|
|
|
|
* <span id="ref-1"><sup>1</sup> Calculating Heuristic Freshness
|
|
[RFC7234 Section 4.2.2][2]</span>
|
|
* Source: [RFC7231 Section 6.3.1][1]
|
|
|
|
[1]: <http://tools.ietf.org/html/rfc7231#section-6.3.1>
|
|
[2]: <http://tools.ietf.org/html/rfc7234#section-4.2.2>
|