User avatar None

Alert triggered
Repository has changes. 06/06/2026
User avatar admin

Resource updated
File “doc/qbk/03_core/10_ssl_tls_shutdown_zh_Hans.qbk” was added. 06/05/2026
User avatar admin

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

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

String added in the repository
Non-Compliant Peers and Unknown Body Length
Non-Compliant Peers and Unknown Body Length
06/05/2026
User avatar admin

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

String added in the repository
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 [@boost:/doc/html/boost_asio/reference/ssl__error__stream_errors.html `net::ssl::error::stream_truncated`] error.
06/05/2026
User avatar admin

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

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

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

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

String added in the repository
error::stream_truncated
error::stream_truncated
06/05/2026
User avatar admin

String added in the repository
A secure SSL/TLS connection requires a proper shutdown process to securely indicate the [@https://en.wikipedia.org/wiki/End-of-file ['EOF]] condition. This process prevents a type of attack known as a [@https://en.wikipedia.org/wiki/Transport_Layer_Security#Truncation_attack ['truncation attack]] in which an attacker can close the underlying transport layer and control the length of the last message in the SSL/TLS connection. A shutdown process consists of exchanging `close_notify` message between two parties. In __Asio__ these steps happen by calling `shutdown()` or `async_shutdown()` on `ssl::stream` object.
A secure SSL/TLS connection requires a proper shutdown process to securely indicate the [@https://en.wikipedia.org/wiki/End-of-file ['EOF]] condition. This process prevents a type of attack known as a [@https://en.wikipedia.org/wiki/Transport_Layer_Security#Truncation_attack ['truncation attack]] in which an attacker can close the underlying transport layer and control the length of the last message in the SSL/TLS connection. A shutdown process consists of exchanging `close_notify` message between two parties. In __Asio__ these steps happen by calling `shutdown()` or `async_shutdown()` on `ssl::stream` object.
06/05/2026
User avatar admin

String added in the repository
SSL/TLS Shutdown
SSL/TLS Shutdown
06/05/2026
User avatar admin

Changes committed
Changes committed 06/05/2026
User avatar admin

Resource updated
Parsing of the “doc/qbk/03_core/10_ssl_tls_shutdown.qbk” file was enforced. 06/05/2026
User avatar None

Alert triggered
No file mask matches. 06/05/2026
User avatar admin

Resource updated
File “doc/qbk/03_core/10_ssl_tls_shutdown.qbk” was added. 06/05/2026
User avatar admin

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

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

Search