Exit Zen
8
string ID 21
type: table cell
English
[link beast.ref.boost__beast__buffers_cat `buffers_cat`]
56/560 · 56
8
string ID 30
type: table cell
English
The host and target parameters become part of the Host field and request-target in the resulting HTTP request. The key is generated by the implementation. Callers who wish to add, modify, or inspect fields may set the ['decorator] option on the stream (described later).
270/2700 · 270
8
string ID 31
type: list
English
* `P` denotes a type that meets the requirements of [*RatePolicy].
* `x` denotes an xvalue of type `P`
* `a` denotes a value of type `P`.
* `n` denotes a value of type `std::size_t`
181/1810 · 181
8
string ID 17
type: table cell
English
[link beast.ref.boost__beast__file_stdio `file_stdio`]
54/540 · 54
8
string ID 46
type: paragraph
English
To provide overloads of teardown for a user-defined type, simply declare the two free functions with the correct signature, accepting a reference to the user-defined type as the stream parameter:
195/1950 · 195
8
string ID 38
type: table cell
English
`value_type`
12/120 · 12
8
string ID 35
type: heading
English
Requirements
12/120 · 12
8
string ID 16
type: variablelist cell
English
Many reviewers feel that HTTP/2 support is an essential feature of a HTTP library. The authors agree that HTTP/2 is important but also feel that the most sensible implementation is one that does not re-use the same network reading and writing interface for 2 as that for 1.0 and 1.1.

The Beast HTTP message model was designed with the new protocol in mind and should be evaluated in that context. There are plans to add HTTP/2 in the future, but there is no rush to do so. Users can work with HTTP/1 now; we should not deny them that functionality today to wait for a newer protocol tomorrow. It is the author's position that there is sufficient value in Beast's HTTP/1-only implementation that the lack of HTTP/2 should not be a barrier to acceptance.

The Beast HTTP message model is suitable for HTTP/2 and can be re-used. The IETF HTTP Working Group adopted message compatibility with HTTP/1.x as an explicit goal. A parser can simply emit full headers after decoding the compressed HTTP/2 headers. The stream ID is not logically part of the message but rather message metadata and should be communicated out-of-band (see below). HTTP/2 sessions begin with a traditional HTTP/1.1 Upgrade similar in fashion to the WebSocket upgrade. An HTTP/2 implementation can use existing Beast.HTTP primitives to perform this handshake.
1328/13280 · 1328
25
string ID 25
type: table cell
English
Name
4/100 · 4
8
string ID 33
type: paragraph
English
These requirements may undergo non-backward compatible
54/540 · 54
8
string ID 22
type: table cell
English
[link beast.ref.boost__beast__websocket__stream_base__timeout.suggested `stream_base::timeout::suggested`]
106/1060 · 106
8
string ID 37
type: heading
English
The io_context
14/140 · 14
8
string ID 54
type: table cell
English
[itemized_list [Timeouts for logical operations] [[@boost:/doc/html/boost_asio/reference/ip__tcp.html `net::ip::tcp`] protocol] [[@boost:/doc/html/boost_asio/reference/executor.html `net::executor`] executor] [[link beast.ref.boost__beast__unlimited_rate_policy `unlimited_rate_policy`] rate limits] ]
301/3010 · 301
8
string ID 49
type: paragraph
English
These relations are true:
25/250 · 25
8
string ID 50
type: table cell
English
Name
4/100 · 4
8
string ID 35
type: paragraph
English
File: [path_link example/websocket/client/sync/websocket_client_sync.cpp websocket_sync_client.cpp]
99/990 · 99
8
string ID 61
type: paragraph
English
When a control callback is registered, it will be invoked for all pings, pongs, and close frames received through either synchronous read functions or asynchronous read functions. The type of frame and payload text are passed as parameters to the control callback. If the frame is a close frame, the close reason may be obtained by calling [link beast.ref.boost__beast__websocket__stream.reason `reason`].
405/4050 · 405
8
string ID 57
type: section title
English
Expect 100-continue (Server) __example__
40/400 · 40
8
string ID 44
type: paragraph
English
A server can also request and verify a client certificate to authenticate the client:
85/850 · 85
8
string ID 44
type: table cell
English
[link beast.ref.boost__beast__async_base `async_base`] [link beast.ref.boost__beast__stable_async_base `stable_async_base`]
123/1230 · 123