Exit Zen
13
string ID 25
type: table code
English
/// A serializer for HTTP/1 requests
template<
class Body,
class Fields = fields
>
using request_serializer = serializer<true, Body, Fields>;
141/1410 · 141
13
string ID 49
type: table cell
English
Expression
10/100 · 10
13
string ID 44
type: table title
English
WebSocket Timeout Interface (2)
31/310 · 31
13
string ID 59
type: paragraph
English
For example, the following code is produces undefined behavior, because the program is attempting to perform two simultaneous reads:
132/1320 · 132
13
string ID 88
type: paragraph
English
Alternatively, we can construct the stream from an executor:
60/600 · 60
13
string ID 97
type: paragraph
English
These containers are capable of representing everything in the model of HTTP requests and responses described in __rfc7230__. Request and response objects are different types. The user can choose the container used to represent the fields. And the user can choose the [*Body] type, which is a concept defining not only the type of `body` member but also the algorithms used to transfer information in and out of that member when performing serialization and parsing.
466/4660 · 466
13
string ID 50
type: table cell
English
When this value is `true`, the stream will support (but not require) the [@https://tools.ietf.org/html/rfc7692 permessage-deflate extension]. Whether or not the stream actually requests or accepts the extension during a handshake depends on a separate configurable option.

When the value is `false` the extension is disabled. Streams will never request the extension in the client role or accept a request for the extension in the server role. An additional benefit of disabling the extension is that compilation will be faster, and the resulting program executable will contain less code.
590/5900 · 590
13
string ID 93
type: paragraph
English
The close function will send a close frame, read and discard incoming message data until receiving a close frame, and then shut down the underlying connection before returning.
176/1760 · 176
13
string ID 95
type: paragraph
English
When a server receives a [@https://tools.ietf.org/html/rfc7231#section-4.3.2 HEAD request], the response should contain the entire header that would be delivered if the method was GET, except that the body is omitted.
217/2170 · 217
13
string ID 65
type: list
English
* [@boost:/doc/html/boost_asio/reference/ssl__context/use_certificate.html `net::ssl::context::use_certificate`]
* [@boost:/doc/html/boost_asio/reference/ssl__context/use_certificate_file.html `net::ssl::context::use_certificate_file`]
* [@boost:/doc/html/boost_asio/reference/ssl__context/use_certificate_chain.html `net::ssl::context::use_certificate_chain`]
* [@boost:/doc/html/boost_asio/reference/ssl__context/use_certificate_chain_file.html `net::ssl::context::use_certificate_chain_file`]
495/4950 · 495
13
string ID 44
type: table cell
English
This function creates a new handler which, when invoked, calls the original handler with the list of bound arguments. Any parameters passed in the invocation will be substituted for placeholders present in the list of bound arguments. Parameters which are not matched to placeholders are silently discarded.

The passed handler and arguments are forwarded into the returned handler, whose associated allocator and associated executor will be the same as those of the original handler.
484/4840 · 484
13
string ID 52
type: paragraph
English
This library is for programmers familiar with __Asio__. Users who
65/650 · 65
13
string ID 77
type: paragraph
English
The listing for a complete, runnable version of this example is in [path_link example/echo-op/echo_op.cpp echo_op.cpp].
119/1190 · 119
13
string ID 46
type: table cell
English
A buffered read stream meets the requirements for synchronous and asynchronous read and write streams, and additionally implements configurable buffering for reads.
164/1640 · 164
14
string ID 47
type: table cell
English
This is a simple, allocating container which lets callers easily build up a set of chunk extensions.
100/1000 · 100
14
string ID 90
type: paragraph
English
Now we will declare our composed operation. There is a considerable amount of necessary boilerplate to get this right, but the result is worth the effort.
154/1540 · 154
14
string ID 25
type: table cell
English
[path_link example/http/client/async-ssl-system-executor/http_client_async_ssl_system_executor.cpp http_client_async_ssl_system_executor.cpp]
141/1410 · 141
14
string ID 21
type: table cell
English
__AsyncWriteStream__
20/200 · 20
14
string ID 40
type: paragraph
English
All synchronous stream operations come in two varieties. One which throws an exception upon error, and another which accepts as the last parameter an argument of type [link beast.ref.boost__beast__error_code `error_code&`]. If an error occurs this argument will be set to contain the error code.
295/2950 · 295
14
string ID 96
type: paragraph
English
Messages may optionally carry a body. The size of the message body is determined by the semantics of the message and the special fields Content-Length and Transfer-Encoding. [@https://tools.ietf.org/html/rfc7230#section-3.3 rfc7230 section 3.3] provides a comprehensive description for how the body length is determined.
320/3200 · 320