User avatar Bstran

Translation changed
[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/16/2026
User avatar Bstran

Translation changed
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/16/2026
User avatar Bstran

Translation changed
[link beast.ref.boost__beast__http__chunk_crlf `chunk_crlf`]
[link beast.ref.boost__beast__http__chunk_crlf `chunk_crlf`]
06/16/2026
User avatar Bstran

Translation changed
A buffer sequence representing a complete chunk body.
A buffer sequence representing a complete chunk body.一个表示完整分块体的缓冲区序列。
06/16/2026
User avatar Bstran

Translation changed
[link beast.ref.boost__beast__http__chunk_body `chunk_body`]
[link beast.ref.boost__beast__http__chunk_body `chunk_body`]
06/16/2026
User avatar Bstran

Translation changed
Description
Description描述
47
06/16/2026
User avatar Bstran

Translation changed
Name
Name名称
47
06/16/2026
User avatar Bstran

Translation changed
Chunking Helpers
Chunking Helpers分块辅助类
06/16/2026
User avatar Bstran

Translation changed
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/16/2026
User avatar Bstran

Translation changed
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.当消息中的 [link beast.ref.boost__beast__http__message.chunked.overload1 `message::chunked`] 返回 `true` 时，__serializer__ 会自动应用分块传输编码。序列化器发出的分块之间的边界由实现定义，分块扩展和尾部字段会被省略。如果应用程序需要对分块边界、扩展和尾部字段进行精确控制，可以使用一组辅助类来手动发送采用分块编码的消息有效载荷。
06/16/2026
User avatar Bstran

Translation changed
Serializing Chunks
Serializing Chunks序列化分块数据
06/16/2026
User avatar Bstran

Translation changed
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对于无法预先确定大小的消息有效载荷，HTTP 版本 1.1 定义了 [@https://tools.ietf.org/html/rfc7230#section-4.1 分块] 传输编码。该编码由零个或多个 [@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.1.1 分块扩展]。最后分块可以包含一个称为 [@https://tools.ietf.org/html/rfc7230#section-4.1.2 分块尾部] 的部分，其中包含额外的 HTTP 字段值。这些字段值在头部中通过 [@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. 字段值中包含“trailers”标记来表示愿意接受尾部字段。
06/16/2026
User avatar Bstran

Translation changed
Chunked Encoding
Chunked Encoding分块传输编码
06/16/2026
User avatar Bstran

Contributor joined
Contributor joined 06/16/2026
User avatar Bstran

Translation completed
Translation completed 06/16/2026
User avatar Bstran

Translation changed
Parsing from a `std::istream` could be implemented using an alternate
Parsing from a从 `std::istream` could be implemented using an alternate解析数据，该操作还可以通过另一种方式实现：
06/16/2026
User avatar Bstran

Translation changed
The standard library provides the type `std::istream` for performing high level read operations on character streams. The variable `std::cin` is based on this input stream. This example uses the buffer oriented interface of __basic_parser__ to build a stream operation which parses an HTTP message from a `std::istream`:
The standard library provides the type `std::istream` for performing high level read operations on character streams. The variable `std::cin` is based on this input stream. This example uses the buffer oriented interface of __basic_parser__ to build a stream operation which parses an HTTP message from a标准库提供 `std::istream` 类型，用于在字符流上执行高层读取操作。`std::cin` 变量就是基于该输入流实现的。本示例借助 __basic_parser__ 的面向缓冲区接口，构建一个流操作，用于从 `std::istream`: 中解析 HTTP 消息：
06/16/2026
User avatar Bstran

Translation changed
Read From std::istream __example__
Read From从 std::istream __example读取 __示例__
06/16/2026
User avatar Bstran

Translation changed
This function sets the maximum allowed size of the header including all field name, value, and delimiter characters and also including the CRLF sequences in the serialized input.
This function sets the maximum allowed size of the header including all field name, value, and delimiter characters and also including the CRLF sequences in the serialized input.该函数用于设置头部允许的最大大小，该大小包括所有字段名、字段值、分隔符字符以及序列化输入中的 CRLF 序列。
06/16/2026
User avatar Bstran

Translation changed
8KB
8KB
06/16/2026

Search