Exit Zen
20
string ID 45
type: table cell
English
`g.prepare(ec)`
15/150 · 15
20
string ID 16
type: variablelist cell
English
Cookies, or managing these types of HTTP headers in general, is the responsibility of higher levels. Beast just tries to get complete messages to and from the calling code. It deals in the HTTP headers just enough to process the message body and leaves the rest to callers. However, for forms and file uploads the symmetric interface of the message class allows HTTP requests to include arbitrary body types including those needed to upload a file or fill out a form.
467/4670 · 467
73
string ID 73
type: table cell
English
Description
11/110 · 11
20
string ID 49
type: table cell
English
`a.put(b,ec)`
13/130 · 13
20
string ID 44
type: table cell
English
[link beast.ref.boost__beast__websocket__stream_base__timeout.idle_timeout `timeout::idle_timeout`]
99/990 · 99
20
string ID 136
type: paragraph
English
Since reads and writes can take place concurrently, it is possible to have two simultaneous logical operations where each operation either only reads, or only writes. The beginning of a new read or write operation will use the most recently set timeout. This will not affect operations that are already outstanding.
315/3150 · 315
20
string ID 147
type: paragraph
English
This function can manipulate the fields common to requests and responses. If it needs to access the other fields, it can use overloads with partial specialization, or in C++17 a `constexpr` expression: ``` template<bool isRequest, class Fields, class Body> void f(message<isRequest, Fields, Body>& msg) {
304/3040 · 304
20
string ID 115
type: paragraph
English
To use WebSockets over SSL, use an instance of the __ssl_stream__ class template as the template type for the stream. The required __io_context__ and __ssl_context__ arguments are forwarded to the wrapped stream's constructor:
226/2260 · 226
20
string ID 140
type: paragraph
English
This example reads from a child process and sends the output back in an HTTP response. The output of the process is sent as it becomes available:
145/1450 · 145
20
string ID 100
type: heading
English
Private Key
11/110 · 11
20
string ID 81
type: paragraph
English
Please visit the [@boost:/more/getting_started.html Boost documentation] for instructions on how to build and link with Boost libraries for your particular environment system.
175/1750 · 175
20
string ID 46
type: table cell
English
[link beast.ref.boost__beast__lowest_layer_type `lowest_layer_type`]
68/680 · 68
21
string ID 101
type: paragraph
English
We demonstrate the use of these objects first by declaring a function which returns the next buffer sequence to use as a chunk body:
132/1320 · 132
21
string ID 25
type: table cell
English
HTTP crawl (asynchronous)
25/250 · 25
63
string ID 63
type: table cell
English
Description
11/110 · 11
21
string ID 95
type: heading
English
Writing
7/100 · 7
21
string ID 110
type: table cell
English
This field allows the sender to indicate desired control options for the current connection. Common values include "close", "keep-alive", and "upgrade".
152/1520 · 152
21
string ID 224
type: paragraph
English
The function [@boost:/doc/html/boost_asio/reference/bind_executor.html `net::bind_executor`] may be used when the caller wants to change the executor of a completion handler.
174/1740 · 174
21
string ID 80
type: table cell
English
Sometimes it is necessary to first send or receive the HTTP header. For example, to read the header and take action before continuing to read the body. These functions use a __parser__ or __serializer__ to read or write the header: [link beast.ref.boost__beast__http__read_header.overload2 `read_header`], [link beast.ref.boost__beast__http__write_header.overload2 `write_header`], [link beast.ref.boost__beast__http__async_read_header `async_read_header`], and [link beast.ref.boost__beast__http__async_write_header `async_write_header`].
539/5390 · 539
21
string ID 66
type: table cell
English
[link beast.ref.boost__beast__http__response_header `response_header`]
70/700 · 70