User avatar Bstran

Translation changed
Supports buffer-oriented blocking reads.
Supports buffer-oriented blocking reads.用于支持面向缓冲区的阻塞读操作。
06/12/2026
User avatar Bstran

Translation changed
__SyncReadStream__
__SyncReadStream__
06/12/2026
User avatar Bstran

Translation changed
Description
Description描述
21
06/12/2026
User avatar Bstran

Translation changed
Concept
Concept概念
06/12/2026
User avatar Bstran

Translation changed
Stream Concepts
Stream Concepts流概念
06/12/2026
User avatar Bstran

Translation changed
A __Stream__ is a communication channel where data is reliably transferred as an ordered sequence of bytes. Streams are either synchronous or asynchronous, and may allow reading, writing, or both. Note that a particular type may model more than one concept. For example, the networking types __socket__ and __ssl_stream__ support both __SyncStream__ and __AsyncStream__. All stream algorithms in Beast are declared as template functions using these concepts:
A __Stream__ is a communication channel where data is reliably transferred as an ordered sequence of bytes. Streams are either synchronous or asynchronous, and may allow reading, writing, or both. Note that a particular type may model more than one concept. For example, the networking types 是一种通信通道，数据以有序字节序列的形式在其中可靠传输。流可分为同步流与异步流，可支持读操作、写操作或两者同时支持。需要注意的是，某个具体类型可能同时符合多个概念模型。例如，网络库中的 __socket__ and与 __ssl_stream__ support both类型同时支持 __SyncStream__ and与 __AsyncStream__. All stream algorithms in Beast are declared as template functions using these concepts: 两种概念。Beast 中的所有流算法均以模板函数形式声明，并使用这些概念进行约束：
06/12/2026
User avatar Bstran

Translation changed
Streams
Streams流类型
06/12/2026
User avatar Bstran

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

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

Translation changed
The following is an example that can read an HTTP response from such a server:
The following is an example that can read an HTTP response from such a server:以下示例用于从这类服务器读取 HTTP 响应：
06/12/2026
User avatar Bstran

Translation changed
This is a rare case and indeed a security issue when HTTPS servers don't perform a proper SSL/TLS shutdown procedure and send an HTTP response message that relies on EOF to determine the end of the body. This is a security concern because without an SSL/TLS shutdown procedure, the EOF is not cryptographically secure, leaving the message body vulnerable to truncation attacks.
This is a rare case and indeed a security issue when HTTPS servers don't perform a proper SSL/TLS shutdown procedure and send an HTTP response message that relies on EOF to determine the end of the body. This is a security concern because without an SSL/TLS shutdown procedure, the EOF is not cryptographically secure, leaving the message body vulnerable to truncation attacks.这种情况比较罕见，但确实存在安全隐患：当 HTTPS 服务器没有执行正确的 SSL/TLS 关闭流程，并且它发送的 HTTP 响应消息需要依靠 EOF 来判断消息体何时结束时，就会产生安全问题。问题的根源在于，缺少 SSL/TLS 关闭流程时，EOF 就不再具有密码学上的安全性，消息体因此容易遭受截断攻击。
06/12/2026
User avatar Bstran

Translation changed
Non-Compliant Peers and Unknown Body Length
Non-Compliant Peers and Unknown Body Length不合规的对等端与未知的消息体长度
06/12/2026
User avatar Bstran

Translation changed
For example, let's assume we are using Beast for communicating with an HTTPS server that doesn't perform a proper SSL/TLS shutdown:
For example, let's assume we are using Beast for communicating with an HTTPS server that doesn't perform a proper SSL/TLS shutdown:例如，假设我们使用 Beast 与一台 HTTPS 服务器通信，而该服务器未执行正确的 SSL/TLS 关闭流程：
06/12/2026
User avatar Bstran

Translation changed
In such scenarios, `http::read` or `http::async_read` operations succeed as they don't need EOF to complete. However, the next operation on the stream would fail with an [@boost:/doc/html/boost_asio/reference/ssl__error__stream_errors.html `net::ssl::error::stream_truncated`] error.
In such scenarios, 在此类场景中，`http::read` or或 `http::async_read` operations succeed as they don't need EOF to complete. However, the next operation on the stream would fail with an操作能够成功完成，因为这些操作无需等待 EOF。然而，如果继续对该流执行下一个操作，则会失败并抛出 [@boost:/doc/html/boost_asio/reference/ssl__error__stream_errors.html `net::ssl::error::stream_truncated`] error.错误。
06/12/2026
User avatar Bstran

Translation changed
* The HTTP message doesn't contain a body, such as any response with a 1xx
* The HTTP message doesn't contain a body, such as any response with a 1xx消息不包含消息体，例如所有 1xx 状态的响应
06/12/2026
User avatar Bstran

Translation changed
* The HTTP message uses chunked transfer encoding, and the final chunk is
* The HTTP message uses chunked transfer encoding, and the final chunk is消息使用分块传输编码，且已接收到最后一个数据块。
06/12/2026
User avatar Bstran

Translation changed
* The HTTP message has a `Content-Length` header, and the body is fully
* HTTP 消息带有 `Content-Length` 头部，且消息体已完整接收。
06/12/2026
User avatar Bstran

Translation changed
* The HTTP message has a `Content-Length` header, and the body is fully
* The HTTP message has a消息带有 `Content-Length` header, and the body is fully头部，且消息体已完整接收。
06/11/2026
User avatar Bstran

Translation changed
There are SSL/TLS implementations that don't perform a proper shutdown process and simply close the underlying transport layer instead. As a result, the EOF condition in these applications is not cryptographically secure and should not be relied upon. However, there are scenarios where an HTTPS client or server doesn't need EOF for determining the end of the last message:
There are SSL/TLS implementations that don't perform a proper shutdown process and simply close the underlying transport layer instead. As a result, the EOF condition in these applications is not cryptographically secure and should not be relied upon. However, there are scenarios where an HTTPS client or server doesn't need EOF for determining the end of the last message:某些 SSL/TLS 实现不执行正确的关闭流程，而是直接关闭底层传输层。因此，这些应用程序中的 EOF 条件不具备密码学安全性，不应依赖于此。然而，在某些场景下，HTTPS 客户端或服务器并不需要依赖 EOF 来确定最后一条消息的结束位置：
06/11/2026
User avatar Bstran

Translation changed
error::stream_truncated
error::stream_truncated
06/11/2026

Search