Exit Zen
7
string ID 39
type: list
English
* The HTTP message doesn't contain a body, such as any response with a 1xx
74/740 · 74
8
string ID 42
type: paragraph
English
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.
283/2830 · 283
9
string ID 48
type: paragraph
English
For example, let's assume we are using Beast for communicating with an HTTPS server that doesn't perform a proper SSL/TLS shutdown:
131/1310 · 131
10
string ID 55
type: heading
English
Non-Compliant Peers and Unknown Body Length
43/430 · 43
11
string ID 57
type: paragraph
English
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.
377/3770 · 377
12
string ID 63
type: paragraph
English
The following is an example that can read an HTTP response from such a server:
78/780 · 78
The translation has come to an end.