Exit Zen
11
string ID 65
type: list
English
* Forgetting to create an object of type __executor_work_guard__ with the
73/730 · 73
11
string ID 19
type: table cell
English
Sets the small buffer size for the file_body. Defaults to 4096.
63/630 · 63
11
string ID 46
type: table cell
English
This stream can be used for synchronous and asynchronous reading and writing. It allows timeouts to be set on logical operations, and can have an executor associated with the stream which is used to invoke completion handlers. This lets you set a strand on the stream once, which is then used for all asynchronous operations automatically.
339/3390 · 339
12
string ID 47
type: table cell
English
A buffer sequence representing the CRLF (`"\r\n"`) delimiter. This class is used when the caller desires to emit the chunk body in two or more individual stream operations.
172/1720 · 172
12
string ID 63
type: paragraph
English
The following is an example that can read an HTTP response from such a server:
78/780 · 78
12
string ID 73
type: paragraph
English
Here we forward declare the composed operation type, and provide the definition of the initiation function object. They are placed in the `detail` namespace since they should not be public:
189/1890 · 189
12
string ID 25
type: table cell
English
[path_link example/http/client/async-local/http_client_async_local.cpp http_client_async_local.cpp]
99/990 · 99
12
string ID 21
type: table cell
English
__AsyncReadStream__
19/190 · 19
12
string ID 16
type: table cell
English
[link beast.ref.boost__beast__http__async_write [*async_write]]
63/630 · 63
12
string ID 75
type: table cell
English
This response has a [@https://tools.ietf.org/html/rfc7231#section-6 200 status code] meaning the operation requested completed successfully. The obsolete reason phrase is "OK". It specifies HTTP version 1.1, and contains a body 13 octets in size with the text "Hello, world!".
276/2760 · 276
12
string ID 125
type: paragraph
English
The __DynamicBuffer__ concept defines a resizable buffer sequence interface. Algorithms may be expressed in terms of dynamic buffers when the memory requirements are not known ahead of time, for example when reading an HTTP message from a stream. Beast provides a well-rounded collection of dynamic buffer types such as [link beast.ref.boost__beast__buffers_adaptor `buffers_adaptor`], [link beast.ref.boost__beast__flat_buffer `flat_buffer`], [link beast.ref.boost__beast__multi_buffer `multi_buffer`], and [link beast.ref.boost__beast__static_buffer `static_buffer`]. The following function reads data from a [link beast.ref.boost__beast__tcp_stream `tcp_stream`] into a dynamic buffer until it encountering a newline character, using [@boost:/doc/html/boost_asio/reference/buffers_iterator.html `net::buffers_iterator`] to treat the contents of the buffer as a range of characters:
884/8840 · 884
12
string ID 74
type: paragraph
English
Interfaces for operating on HTTP messages are structured into several layers. The highest level provides ease of use, while lower levels provide progressively more control, options, and flexibility. At the lowest level customization points are provided, where user defined types can replace parts of the implementation. The layers are arranged thusly:
351/3510 · 351
12
string ID 51
type: paragraph
English
The container offers value semantics including move and copy if supported by __Body__ and __Fields__. User defined template function parameters can accept any message, or can use partial specialization to accept just requests or responses. The default __fields__ is a provided associative container using the standard allocator and supporting modification and inspection of fields. As per __rfc7230__, a non-case-sensitive comparison is used for field names. User defined types for fields are possible. The `Body` type determines the type of the container used to represent the body as well as the algorithms for transferring buffers to and from the container. The library comes with a collection of common body types. As with fields, user defined body types are possible.
772/7720 · 772
12
string ID 29
type: table code
English
/// An HTTP/1 parser for producing a message.
template<
bool isRequest, // `true` to parse an HTTP request
class Body, // The Body type for the resulting message
class Allocator = std::allocator<char>> // The type of allocator for the header
class parser
: public basic_parser<...>;
334/3340 · 334
12
string ID 63
type: list
English
* [issue 3002] Conditionally defined `immediate_executor_type` in `async_base`
* [issue 2999] Used `handshake_timeout` for closing handshake during read operations
* [issue 3003] Added missing `cstdint` header to `detail/cpu_info.hpp`
* [issue 3016] Fixed `std::is_trivial` deprecation warnings
* [issue 3019] Fixed `-Wmaybe-uninitialized` warnings
348/3480 · 348
12
string ID 30
type: table cell
English
`B::value_type`
15/150 · 15
12
string ID 85
type: paragraph
English
This container is the base class template used to represent HTTP messages. It uses a "tag" type style specializations for a variety of trait classes, allowing for customization of the various parts of the message. For example, a user specializes `headers_container<T>` to determine what container type holds the header fields. We note some problems with the container declaration:
380/3800 · 380
12
string ID 36
type: table cell
English
`F::writer`
11/110 · 11
12
string ID 30
type: table cell
English
[link beast.ref.boost__beast__http__basic_parser.skip.overload2 `skip`]
71/710 · 71
12
string ID 38
type: list
English
* __SyncReadStream__
* __SyncWriteStream__
42/420 · 42