A subclass of __basic_parser__ can be invoked directly, without using the provided stream operations. This could be useful for implementing algorithms on objects whose interface does not conform to __Stream__. For example, a [@http://zeromq.org/ *ZeroMQ* socket]. The basic parser interface is interactive; the caller invokes the function [link beast.ref.boost__beast__http__basic_parser.put `basic_parser::put`] repeatedly with buffers until an error occurs or the parsing is done. The function [link beast.ref.boost__beast__http__basic_parser.put_eof `basic_parser::put_eof`] Is used when the caller knows that there will never be more data (for example, if the underlying connection is closed),

__video__ contains video presentation content

An algorithm should never depend on the way that incoming or outgoing

These requirements may undergo non-backward compatible

For portability reasons, networking does not provide timeouts

* The HTTP message uses chunked transfer encoding, and the final chunk is

* `B` is a type meeting the requirements of [*Body].
* `m` is a value of type `message<b,B,F>` where `b` is a `bool` value

`file` is a type alias to one of the following implementations, depending on what is available on the target platform.

* `m` is an instance of [link beast.ref.boost__beast__file_mode `file_mode`]
* `n` is a number of bytes, convertible to `std::size_t`
* `o` is a byte offset in the file, convertible to `std::uint64_t`
* `b` is any non-const pointer to memory
* `c` is any possibly-const pointer to memory
* `ec` is a reference of type [link beast.ref.boost__beast__error_code `error_code`]

* `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`

`const_buffer` and `mutable_buffer` are preferred over `std::span<byte>`

* Forgetting to provide `executor_type` and `get_executor` for the

* Forgetting to create an object of type __executor_work_guard__ with the

* There is no way to defer the commitment of the type for `body_` to

The same message could be sent in two or more frames thusly.

The __basic_parser__ and classes derived from it handle octet streams

Other Implementations of __DynamicBuffer__ may avoid parser

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.

The private key of a certificate is required during the SSL/TLS handshake to prove that the certificate's provider is its rightful owner

A metafunction to return the type of the lowest layer used in a type representing a stack of stream layers. This is the type of reference returned by [link beast.ref.boost__beast__get_lowest_layer `get_lowest_layer`]