butterfly/kb
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
1467547cab
kb/data/developer.mozilla.org/en-US/docs/Glossary/HTTP_Content-0.md

11 KiB
Raw Blame History

title chunk source category tags date_saved instance
HTTP content - Glossary | MDN 1/3 https://developer.mozilla.org/en-US/docs/Glossary/HTTP_Content reference web, html, css, javascript, documentation 2026-05-05T05:33:43.615414+00:00 kb-cron

MDN HTML HTML: Markup language

HTML reference

HTML guides

Markup languages

CSS CSS: Styling language

CSS reference

CSS guides

Layout cookbook

JavaScriptJS JavaScript: Scripting language

JS reference

JS guides

Web APIs Web APIs: Programming interfaces

Web API reference

Web API guides

All All web technology

Technologies

Topics

Learn Learn web development

Frontend developer course

Learn HTML

Learn CSS

Learn JavaScript

Tools Discover our tools

About Get to know MDN better

Blog

  1. Glossary
  2. HTTP content

HTTP content

In HTTP messages, the content describes the 'information' conveyed in the message body (which follows the header section), after any message framing from HTTP/1.1 chunked transfer encoding has been removed. This was referred to as a "payload" in HTTP/1.1, but message "content" distinguishes from frame payloads in HTTP/2 and HTTP/3 where the data in a single frame could be header data, body data, or other control information. The purpose of message content in HTTP requests and responses depends on the request method and response status code. For example, in a PUT request, the content represents the desired state of the resource, but in a POST request, it is information to be processed. A 200 OK response to a GET request shows the current state of the resource, while an error response describes the error. Some responses, like those to HEAD requests or 204 No Content and 304 Not Modified status codes, do not include content at all. In the following HTTP/1.1 response, the message body contains the content Mozilla Developer Network: In the next HTTP/1.1 response, transfer encoding encodes the data into chunks. The content is still Mozilla Developer Network in the end, but the message body includes different message data to separate the chunks:

In this article

See also