Exit Zen
19
string ID 66
type: table cell
English
[link beast.ref.boost__beast__http__request_header `request_header`]
68/680 · 68
71
string ID 71
type: table title
English
Parser Stream Operations
24/240 · 24
19
string ID 30
type: table cell
English
`std::uint64_t`
15/150 · 15
19
string ID 121
type: list
English
* The specialized trait classes generate a proliferation of small
65/650 · 65
19
string ID 39
type: table cell
English
The implementation calls this constructor to indicate that the fields being serialized form part of an HTTP response. The lifetime of `f` is guaranteed to end no earlier than after the `W` is destroyed.
202/2020 · 202
19
string ID 36
type: table cell
English
Returns the target string. The implementation only calls this function for request headers.
91/910 · 91
19
string ID 30
type: table cell
English
This function sets the maximum allowed size of the header including all field name, value, and delimiter characters and also including the CRLF sequences in the serialized input.
178/1780 · 178
19
string ID 75
type: paragraph
English
The implementation takes ownership by decay-copy of the invocable object used as the decorator. Move-only types are possible:
125/1250 · 125
19
string ID 21
type: table cell
English
This function returns an iterable range representing the passed buffer sequence. The values obtained when iterating the range will always be a constant buffer, unless the underlying buffer sequence is mutable, in which case the value obtained when iterating will be a mutable buffer. It is intended as a notational convenience when writing a ['range-for] statement over a buffer sequence.

The function [link beast.ref.boost__beast__buffers_range_ref `buffers_range`] maintains a copy of the buffer sequence, while [link beast.ref.boost__beast__buffers_range_ref `buffers_range_ref`] maintains a reference (in this case, the caller must ensure that the lifetime of the referenced buffer sequence extends until the range object is destroyed).
741/7410 · 741
19
string ID 117
type: heading
English
Handshake Buffering
19/190 · 19
19
string ID 36
type: table cell
English
This function is called by the implementation to determine the maximum number of allowed bytes to be transferred in the next read operation. The actual number of bytes subsequently transferred may be less than this number.

If the policy returns a value of zero, the read operation will asynchronously wait until the next timer interval before retrying. When the retry occurs, this function will be called again.
412/4120 · 412
19
string ID 95
type: section title
English
File Body __example__
21/210 · 21
19
string ID 45
type: table cell
English
Called to ask the generator for its completion status.

A generator has completed when no new buffer will be produced and previously produced buffers have been fully consumed.

[*Note:] The result of invoking `prepare` on `g` once it has completed is unspecified.
263/2630 · 263
19
string ID 16
type: variablelist cell
English
"HTTP Cookies? Forms/File Uploads?"
35/350 · 35
19
string ID 49
type: table cell
English
Called once to fully initialize the object before any calls to `put`. The message body is valid before entering this function, and remains valid until the reader is destroyed. The value of `n` will be set to the content length of the body if known, otherwise `n` will be equal to `boost::none`. Implementations of [*BodyReader] may use this information to optimize allocation.

The function will ensure that `!ec` is `true` if there was no error or set to the appropriate error code if there was one.
500/5000 · 500
19
string ID 44
type: table cell
English
This is the amount of time after which a handshake will time out. The handshake timeout applies to client handshakes, server handshakes, as well as the websocket closing handshake performed when either end of the connection wish to shut down. The value returned by [link beast.ref.boost__beast__websocket__stream_base.none `stream_base::none()`] may be assigned to disable this timeout.
386/3860 · 386
19
string ID 129
type: paragraph
English
Timeouts apply to the logical operation, expressed as a series of asynchronous calls, rather than just the next call. This code reads a line from the stream and writes it back. Both the read and the write must complete within 30 seconds from when the timeout was set; the timer is not reset between operations.
310/3100 · 310
19
string ID 141
type: paragraph
English
Now we can declare a function which takes any message as a parameter: ``` template<bool isRequest, class Fields, class Body> void f(message<isRequest, Fields, Body>& msg); ```
175/1750 · 175
19
string ID 113
type: heading
English
Using SSL
9/100 · 9
19
string ID 135
type: paragraph
English
To enable these use-cases, the body type __buffer_body__ is provided. This body uses a caller-provided pointer and size instead of an owned container. To use this body, instantiate an instance of the serializer and fill in the pointer and size fields before calling a stream write function.
290/2900 · 290