User avatar admin

String added in the repository
[link beast.ref.boost__beast__http__make_chunk `make_chunk`]

[link beast.ref.boost__beast__http__make_chunk_last `make_chunk_last`]
[link beast.ref.boost__beast__http__make_chunk `make_chunk`]

[link beast.ref.boost__beast__http__make_chunk_last `make_chunk_last`]
06/05/2026
User avatar admin

String added in the repository
A buffer sequence representing a last chunk. The last chunk indicates the end of the chunked message payload, and may contain optional trailer fields.
A buffer sequence representing a last chunk. The last chunk indicates the end of the chunked message payload, and may contain optional trailer fields.
06/05/2026
User avatar admin

String added in the repository
[link beast.ref.boost__beast__http__chunk_last `chunk_last`]
[link beast.ref.boost__beast__http__chunk_last `chunk_last`]
06/05/2026
User avatar admin

String added in the repository
A buffer sequence representing a hex-encoded chunk size, followed by an optional set of chunk extensions, including the terminating CRLF (`"\r\n"`) delimiter which precedes the chunk body. This class is used when the caller desires to emit the chunk body in two or more individual stream operations.
A buffer sequence representing a hex-encoded chunk size, followed by an optional set of chunk extensions, including the terminating CRLF (`"\r\n"`) delimiter which precedes the chunk body. This class is used when the caller desires to emit the chunk body in two or more individual stream operations.
06/05/2026
User avatar admin

String added in the repository
[link beast.ref.boost__beast__http__chunk_header `chunk_header`]
[link beast.ref.boost__beast__http__chunk_header `chunk_header`]
06/05/2026
User avatar admin

String added in the repository
This is a simple, allocating container which lets callers easily build up a set of chunk extensions.
This is a simple, allocating container which lets callers easily build up a set of chunk extensions.
06/05/2026
User avatar admin

String added in the repository
[link beast.ref.boost__beast__http__chunk_extensions `chunk_extensions`]

[link beast.ref.boost__beast__http__basic_chunk_extensions `basic_chunk_extensions`]
[link beast.ref.boost__beast__http__chunk_extensions `chunk_extensions`]

[link beast.ref.boost__beast__http__basic_chunk_extensions `basic_chunk_extensions`]
06/05/2026
User avatar admin

String added in the repository
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.
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.
06/05/2026
User avatar admin

String added in the repository
[link beast.ref.boost__beast__http__chunk_crlf `chunk_crlf`]
[link beast.ref.boost__beast__http__chunk_crlf `chunk_crlf`]
06/05/2026
User avatar admin

String added in the repository
A buffer sequence representing a complete chunk body.
A buffer sequence representing a complete chunk body.
06/05/2026
User avatar admin

String added in the repository
[link beast.ref.boost__beast__http__chunk_body `chunk_body`]
[link beast.ref.boost__beast__http__chunk_body `chunk_body`]
06/05/2026
User avatar admin

String added in the repository
Description
Description
47
06/05/2026
User avatar admin

String added in the repository
Name
Name
47
06/05/2026
User avatar admin

String added in the repository
Chunking Helpers
Chunking Helpers
06/05/2026
User avatar admin

String added in the repository
To use these helper classes, first serialize the header portion of the message using the standard interface. Then prepare the buffers, chunk extensions, and desired trailers, and use them with these helpers:
To use these helper classes, first serialize the header portion of the message using the standard interface. Then prepare the buffers, chunk extensions, and desired trailers, and use them with these helpers:
06/05/2026
User avatar admin

String added in the repository
The __serializer__ automatically applies the chunked transfer encoding when a message returns `true` from [link beast.ref.boost__beast__http__message.chunked.overload1 `message::chunked`]. The boundaries between chunks emitted by the serializer are implementation defined. Chunk extensions and trailers are omitted. Applications which need precise control over the chunk boundaries, extensions, and trailers may use a set of helper classes which enable manual emission of message payloads using chunk encoding.
The __serializer__ automatically applies the chunked transfer encoding when a message returns `true` from [link beast.ref.boost__beast__http__message.chunked.overload1 `message::chunked`]. The boundaries between chunks emitted by the serializer are implementation defined. Chunk extensions and trailers are omitted. Applications which need precise control over the chunk boundaries, extensions, and trailers may use a set of helper classes which enable manual emission of message payloads using chunk encoding.
06/05/2026
User avatar admin

String added in the repository
Serializing Chunks
Serializing Chunks
06/05/2026
User avatar admin

String added in the repository
For message payloads whose size is not known ahead of time, HTTP version 1.1 defines the [@https://tools.ietf.org/html/rfc7230#section-4.1 ['chunked]] transfer coding. This coding consists of zero or more [@https://tools.ietf.org/html/rfc7230#section-4.1 ['chunked bodies]], followed by a [@https://tools.ietf.org/html/rfc7230#section-4.1 ['last chunk]]. Each chunked body may contain optional application-defined, connection-specific [@https://tools.ietf.org/html/rfc7230#section-4.1.1 ['chunk-extensions]]. The last chunk may contain additional HTTP field values in a section of the last chunk called a [@https://tools.ietf.org/html/rfc7230#section-4.1.2 ['chunk-trailer]]. The field values are "promised" in the header as a comma delimited list of field names in the [@https://tools.ietf.org/html/rfc7230#section-4.4 [*Trailer]] field value. Clients indicate their willingness to accept trailers by including the "trailers" token in the [@https://tools.ietf.org/html/rfc7230#section-4.3 [*TE]] field value.
For message payloads whose size is not known ahead of time, HTTP version 1.1 defines the [@https://tools.ietf.org/html/rfc7230#section-4.1 ['chunked]] transfer coding. This coding consists of zero or more [@https://tools.ietf.org/html/rfc7230#section-4.1 ['chunked bodies]], followed by a [@https://tools.ietf.org/html/rfc7230#section-4.1 ['last chunk]]. Each chunked body may contain optional application-defined, connection-specific [@https://tools.ietf.org/html/rfc7230#section-4.1.1 ['chunk-extensions]]. The last chunk may contain additional HTTP field values in a section of the last chunk called a [@https://tools.ietf.org/html/rfc7230#section-4.1.2 ['chunk-trailer]]. The field values are "promised" in the header as a comma delimited list of field names in the [@https://tools.ietf.org/html/rfc7230#section-4.4 [*Trailer]] field value. Clients indicate their willingness to accept trailers by including the "trailers" token in the [@https://tools.ietf.org/html/rfc7230#section-4.3 [*TE]] field value.
06/05/2026
User avatar admin

String added in the repository
Chunked Encoding
Chunked Encoding
06/05/2026
User avatar admin

Changes committed
Changes committed 06/05/2026

Search