Skip to content

Commit

Permalink
Correct link format
Browse files Browse the repository at this point in the history
The bot turned my absolute link into a relative link.  I should have done that myself.

Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
  • Loading branch information
crossaw and github-actions[bot] authored Jan 10, 2025
1 parent bb19090 commit 4e5d432
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion files/en-us/glossary/payload_body/index.md
Original file line number Diff line number Diff line change
Expand Up @@ -8,6 +8,6 @@ page-type: glossary-definition

Prior to June 2022, the **payload body** or **payload** was the resource representation being transferred in an HTTP Message Body, stripped of any [transfer encoding](/en-US/docs/Web/HTTP/Headers/Transfer-Encoding). With no transfer encoding, the _payload body_ and _message body_ are the same thing. Representation data could also be transferred in the HTTP Header, but such data would not be regarded as "payload".

With the release of RFC 9110, the word **content** replaces the word **payload**. See [**HTTP content**](https://developer.mozilla.org/en-US/docs/Glossary/HTTP_Content).
With the release of RFC 9110, the word **content** replaces the word **payload**. See [**HTTP content**](/en-US/docs/Glossary/HTTP_Content).

For more information see [RFC 7230, section 3.3: Message Body](https://datatracker.ietf.org/doc/html/rfc7230#section-3.3), [RFC 7231, section 3: Representations](https://datatracker.ietf.org/doc/html/rfc7231#section-3), and [RFC 9110, appendix B.3: Changes from RFC 7231](https://datatracker.ietf.org/doc/html/rfc9110#name-changes-from-rfc-7231).

0 comments on commit 4e5d432

Please sign in to comment.