Exit Zen
30
string ID 120
type: table cell
English
[link beast.ref.boost__beast__http__empty_body `empty_body`]
60/600 · 60
31
string ID 120
type: table cell
English
A special body with an empty `value_type` indicating that the message has no body. Messages with this body may be serialized and parsed; however, body octets received while parsing a message with this body will generate a unique error.
235/2350 · 235
32
string ID 120
type: table cell
English
[link beast.ref.boost__beast__http__file_body `file_body`]

[link beast.ref.boost__beast__http__basic_file_body `basic_file_body`]
130/1300 · 130
33
string ID 120
type: table cell
English
This body is represented by a file opened for either reading or writing. Messages with this body may be serialized and parsed. HTTP algorithms will use the open file for reading and writing, for streaming and incremental sends and receives.
240/2400 · 240
34
string ID 120
type: table cell
English
[link beast.ref.boost__beast__http__span_body `span_body`]
58/580 · 58
35
string ID 120
type: table cell
English
A body whose `value_type` is a [@boost:/libs/core/doc/html/core/span.html `span`], a non-owning reference to a single linear buffer of bytes. Messages with this body type may be serialized and parsed.
200/2000 · 200
36
string ID 120
type: table cell
English
[link beast.ref.boost__beast__http__string_body `string_body`]

[link beast.ref.boost__beast__http__basic_string_body `basic_string_body`]
138/1380 · 138
37
string ID 120
type: table cell
English
A body whose `value_type` is `std::basic_string` or `std::string`. Insertion complexity is amortized constant time, while capacity grows geometrically. Messages with this body type may be serialized and parsed. This is the type of body used in the examples.
257/2570 · 257
38
string ID 120
type: table cell
English
[link beast.ref.boost__beast__http__vector_body `vector_body`]
62/620 · 62
39
string ID 120
type: table cell
English
A body whose `value_type` is `std::vector`. Insertion complexity is amortized constant time, while capacity grows geometrically. Messages with this body type may be serialized and parsed.
187/1870 · 187
40
string ID 186
type: heading
English
Usage
5/100 · 5
41
string ID 188
type: paragraph
English
These examples show how to create and fill in request and response objects: Here we build an [@https://tools.ietf.org/html/rfc7231#section-4.3.1 HTTP GET] request with an empty message body:
190/1900 · 190
42
string ID 193
type: table title
English
Create Request
14/140 · 14
193
string ID 193
type: table cell
English
Statements
10/100 · 10
193
string ID 193
type: table cell
English
Serialized Result
17/170 · 17
45
string ID 193
type: table cell
English
[http_snippet_2]
16/160 · 16
46
string ID 193
type: table code
English
GET /index.htm HTTP/1.1\r\n
Accept: text/html\r\n
User-Agent: Beast\r\n
\r\n
76/760 · 76
47
string ID 207
type: paragraph
English
In this code we create an HTTP response with a status code indicating success. This message has a body with a non-zero length. The function [link beast.ref.boost__beast__http__message.prepare_payload `message::prepare_payload`] automatically sets the Content-Length or Transfer-Encoding field depending on the content and type of the `body` member. Use of this function is optional; these fields may also be set explicitly.
423/4230 · 423
48
string ID 214
type: table title
English
Create Response
15/150 · 15
214
string ID 214
type: table cell
English
Statements
10/100 · 10