The translation has come to an end.
User avatar None

Alert triggered
Broken project website URL 07/06/2026
User avatar None

Resource updated
Parsing of the “doc/qbk/04_http/07_parser_buffers_zh_Hans.qbk” file was enforced. 06/26/2026
User avatar None

String updated in the repository
`false`
`false`
30
06/26/2026
User avatar None

Resource updated
Parsing of the “doc/qbk/04_http/07_parser_buffers.qbk” file was enforced. 06/26/2026
User avatar weblate:commit

Changes committed
Changes committed 06/17/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
User avatar Bstran

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

Translation changed
This function sets the maximum allowed size of the content body. When a body larger than the specified size is detected, an error is generated and parsing terminates. This setting helps protect servers from resource exhaustion attacks. The default limit when parsing requests is 1MB, and for parsing responses 8MB.
This function sets the maximum allowed size of the content body. When a body larger than the specified size is detected, an error is generated and parsing terminates. This setting helps protect servers from resource exhaustion attacks. The default limit when parsing requests is 1MB, and for parsing responses该函数用于设置消息体允许的最大大小。一旦检测到消息体超过该限制，就会触发错误并终止解析过程。这项设置有助于防范资源耗尽攻击，提升服务器安全性。解析请求时的默认限制为 1MB，解析响应时的默认限制为 8MB.。
06/16/2026
User avatar Bstran

Translation changed
1MB/8MB
1MB/8MB
06/16/2026
User avatar Bstran

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

Translation changed
This option controls whether or not the parser expects to see an HTTP body, regardless of the presence or absence of certain fields such as Content-Length or a chunked Transfer-Encoding. Depending on the request, some responses do not carry a body. For example, a 200 response to a [@https://tools.ietf.org/html/rfc7231#section-4.3.6 CONNECT] request from a tunneling proxy, or a response to a [@https://tools.ietf.org/html/rfc7231#section-4.3.2 HEAD] request. In these cases, callers may use this function inform the parser that no body is expected. The parser will consider the message complete after the header has been received.
This option controls whether or not the parser expects to see an HTTP body, regardless of the presence or absence of certain fields such as Content-Length or a chunked Transfer-Encoding. Depending on the request, some responses do not carry a body. For example, a 200 response to a [@https://tools.ietf.org/html/rfc7231#section-4.3.6 CONNECT] request from a tunneling proxy, or a response to a [@https://tools.ietf.org/html/rfc7231#section-4.3.2 HEAD] request. In these cases, callers may use this function inform the parser that no body is expected. The parser will consider the message complete after the header has been received.该选项用于控制解析器是否期待接收 HTTP 消息体，这个判断独立于 Content-Length 或分块传输编码等字段是否存在。某些类型的响应本身就不包含消息体。例如，隧道代理对 CONNECT 请求返回的 200 响应，或者对 HEAD 请求的响应。在这些场景下，调用方可以使用该函数告知解析器不需要消息体。解析器在收到头部后就会将消息视为已完整接收。
06/16/2026
User avatar Bstran

Translation changed
[link beast.ref.boost__beast__http__basic_parser.skip.overload2 `skip`]
[link beast.ref.boost__beast__http__basic_parser.skip.overload2 `skip`]
06/16/2026
User avatar Bstran

Translation changed
Normally the parser returns after successfully parsing a structured element (header, chunk header, or chunk body) even if there are octets remaining in the input. This is necessary when attempting to parse the header first, or when the caller wants to inspect information which may be invalidated by subsequent parsing, such as a chunk extension. The `eager` option controls whether the parser keeps going after parsing structured element if there are octets remaining in the buffer and no error occurs. This option is automatically set or cleared during certain stream operations to improve performance with no change in functionality.
Normally the parser returns after successfully parsing a structured element (header, chunk header, or chunk body) even if there are octets remaining in the input. This is necessary when attempting to parse the header first, or when the caller wants to inspect information which may be invalidated by subsequent parsing, such as a chunk extension. The `eager` option controls whether the parser keeps going after parsing structured element if there are octets remaining in the buffer and no error occurs. This option is automatically set or cleared during certain stream operations to improve performance with no change in functionality.在通常处理流程中，即便输入数据中仍存在未解析的八位字节，解析器在成功解析一个结构化元素（如头部、分块头部或分块体）后也会立即返回。此行为在需要先解析头部，或调用方希望在后续解析可能覆盖某些信息（例如分块扩展）之前进行检查的场景下非常关键。`eager` 选项用于控制解析器在成功解析结构化元素后，若缓冲区中仍存在剩余字节且未发生错误，是否继续执行解析。该选项会在特定流操作中被自动启用或禁用，以便在不影响功能的前提下优化性能。
06/16/2026
User avatar Bstran

Translation changed
`false`
`false` —— 假值
30
06/16/2026
User avatar Bstran

Translation added
`false`
`false` —— 假值
30
06/16/2026

Search