1843 strings

Translation Source string Target string
Boost Beast Translation (zh_Hans)/Doc / Qbk / 08 Design / 4 Faq (qbk) — English
Beast uses more than Boost.Asio, it depends on various other parts of Boost. The standalone Asio is currently farther ahead than the Boost version. Keeping Beast maintained against both versions of Asio is beyond the resources of the author at the present time. Compatibility with non-Boost libraries should not be an acceptance criteria. Beast is currently designed to be a part of Boost: nothing more, nothing less. Looking at the bigger picture, it is the author's goal to propose this library for standardization. A logical track for achieving this is as follows:

[ordered_list [ Boost library acceptance. ][ Port to the Boost.Asio version of Networking-TS (This has to wait until Boost's version of Asio is updated). ][ Wait for Networking-TS to become an official part of C++. ][ Port to the standard library versions of networking (gcc, clang, msvc). ][ Develop proposed language (This can happen concurrently with steps 3 and 4) ]]
Beast uses more than Boost.Asio, it depends on various other parts of Boost. The standalone Asio is currently farther ahead than the Boost version. Keeping Beast maintained against both versions of Asio is beyond the resources of the author at the present time. Compatibility with non-Boost libraries should not be an acceptance criteria. Beast is currently designed to be a part of Boost: nothing more, nothing less. Looking at the bigger picture, it is the author's goal to propose this library for standardization. A logical track for achieving this is as follows:

[ordered_list [ Boost library acceptance. ][ Port to the Boost.Asio version of Networking-TS (This has to wait until Boost's version of Asio is updated). ][ Wait for Networking-TS to become an official part of C++. ][ Port to the standard library versions of networking (gcc, clang, msvc). ][ Develop proposed language (This can happen concurrently with steps 3 and 4) ]]
Boost Beast Translation (zh_Hans)/Doc / Qbk / 08 Design / 4 Faq (qbk) — English
"You need benchmarks!"
"You need benchmarks!"
Boost Beast Translation (zh_Hans)/Doc / Qbk / 08 Design / 4 Faq (qbk) — English
The energy invested in Beast went into the design of the interfaces, not performance. That said, the most sensitive parts of Beast have been optimized or designed with optimization in mind. The slow parts of WebSocket processing have been optimized, and the HTTP parser design is lifted from another extremely popular project which has performance as a design goal (see [@https://github.com/h2o/picohttpparser]).

From: [@http://www.boost.org/development/requirements.html]

"Aim first for clarity and correctness; optimization should be only a secondary concern in most Boost libraries."

As the library matures it will undergo optimization passes; benchmarks will logically accompany this process. There is a small benchmarking program included in the tests which compares the performance of Beast's parser to the NodeJS reference parser, as well as some benchmarks which compare the performance of various Beast dynamic buffer implementations against Asio's.
The energy invested in Beast went into the design of the interfaces, not performance. That said, the most sensitive parts of Beast have been optimized or designed with optimization in mind. The slow parts of WebSocket processing have been optimized, and the HTTP parser design is lifted from another extremely popular project which has performance as a design goal (see [@https://github.com/h2o/picohttpparser]).

From: [@http://www.boost.org/development/requirements.html]

"Aim first for clarity and correctness; optimization should be only a secondary concern in most Boost libraries."

As the library matures it will undergo optimization passes; benchmarks will logically accompany this process. There is a small benchmarking program included in the tests which compares the performance of Beast's parser to the NodeJS reference parser, as well as some benchmarks which compare the performance of various Beast dynamic buffer implementations against Asio's.
Boost Beast Translation (zh_Hans)/Doc / Qbk / 08 Design / 4 Faq (qbk) — English
"Beast is a terrible name!"
"Beast is a terrible name!"
Boost Beast Translation (zh_Hans)/Doc / Qbk / 08 Design / 4 Faq (qbk) — English
The name "Boost.Http" or "Boost.WebSocket" would mislead users into believing they could perform an HTTP request on a URL or put up a WebSocket client or server in a couple of lines of code. Where would the core utilities go? Very likely it would step on the owner of Boost.Asio's toes to put things in the boost/asio directory; at the very least, it would create unrequested, additional work for the foreign repository.

"Beast" is sufficiently vague as to not suggest any particular functionality, while acting as a memorable umbrella term for a family of low level containers and algorithms. People in the know or with a need for low-level network protocol operations will have no trouble finding it, and the chances of luring a novice into a bad experience are greatly reduced. There is precedent for proper names: "Hana", "Fusion", "Phoenix", and "Spirit" come to mind. Is "Beast" really any worse than say, "mp11" for example? Beast also already has a growing body of users and attention from the open source community, the name Beast comes up in reddit posts and StackOverflow as the answer to questions about which HTTP or WebSocket library to use.
The name "Boost.Http" or "Boost.WebSocket" would mislead users into believing they could perform an HTTP request on a URL or put up a WebSocket client or server in a couple of lines of code. Where would the core utilities go? Very likely it would step on the owner of Boost.Asio's toes to put things in the boost/asio directory; at the very least, it would create unrequested, additional work for the foreign repository.

"Beast" is sufficiently vague as to not suggest any particular functionality, while acting as a memorable umbrella term for a family of low level containers and algorithms. People in the know or with a need for low-level network protocol operations will have no trouble finding it, and the chances of luring a novice into a bad experience are greatly reduced. There is precedent for proper names: "Hana", "Fusion", "Phoenix", and "Spirit" come to mind. Is "Beast" really any worse than say, "mp11" for example? Beast also already has a growing body of users and attention from the open source community, the name Beast comes up in reddit posts and StackOverflow as the answer to questions about which HTTP or WebSocket library to use.
Boost Beast Translation (zh_Hans)/Doc / Qbk / 08 Design / 4 Faq (qbk) — English
"Some more advanced examples, e.g. including TLS with client/server certificates would help."
"Some more advanced examples, e.g. including TLS with client/server certificates would help."
Boost Beast Translation (zh_Hans)/Doc / Qbk / 08 Design / 4 Faq (qbk) — English
The server-framework example demonstrates how to implement a server that supports TLS using certificates. There are also websocket and HTTP client examples which use TLS. Furthermore, management of certificates is beyond the scope of the public interfaces of the library. Asio already provides documentation, interfaces, and examples for performing these tasks - Beast does not intend to reinvent them or to redundantly provide this information.
The server-framework example demonstrates how to implement a server that supports TLS using certificates. There are also websocket and HTTP client examples which use TLS. Furthermore, management of certificates is beyond the scope of the public interfaces of the library. Asio already provides documentation, interfaces, and examples for performing these tasks - Beast does not intend to reinvent them or to redundantly provide this information.
Boost Beast Translation (zh_Hans)/Doc / Qbk / 08 Design / 4 Faq (qbk) — English
"A built-in HTTP router?"
"A built-in HTTP router?"
Boost Beast Translation (zh_Hans)/Doc / Qbk / 08 Design / 4 Faq (qbk) — English
We presume this means a facility to match expressions against the URI in HTTP requests, and dispatch them to calling code. The authors feel that this is a responsibility of higher level code. Beast does not try to offer a web server. That said, the server-framework example has a concept of request routing called a Service. Two services are provided, one for serving files and the other for handling WebSocket upgrade requests.
We presume this means a facility to match expressions against the URI in HTTP requests, and dispatch them to calling code. The authors feel that this is a responsibility of higher level code. Beast does not try to offer a web server. That said, the server-framework example has a concept of request routing called a Service. Two services are provided, one for serving files and the other for handling WebSocket upgrade requests.
Boost Beast Translation (zh_Hans)/Doc / Qbk / 08 Design / 4 Faq (qbk) — English
"HTTP Cookies? Forms/File Uploads?"
"HTTP Cookies? Forms/File Uploads?"
Boost Beast Translation (zh_Hans)/Doc / Qbk / 08 Design / 4 Faq (qbk) — English
Cookies, or managing these types of HTTP headers in general, is the responsibility of higher levels. Beast just tries to get complete messages to and from the calling code. It deals in the HTTP headers just enough to process the message body and leaves the rest to callers. However, for forms and file uploads the symmetric interface of the message class allows HTTP requests to include arbitrary body types including those needed to upload a file or fill out a form.
Cookies, or managing these types of HTTP headers in general, is the responsibility of higher levels. Beast just tries to get complete messages to and from the calling code. It deals in the HTTP headers just enough to process the message body and leaves the rest to callers. However, for forms and file uploads the symmetric interface of the message class allows HTTP requests to include arbitrary body types including those needed to upload a file or fill out a form.
Boost Beast Translation (zh_Hans)/Doc / Qbk / 08 Design / 4 Faq (qbk) — English
"...supporting TLS (is this a feature? If not this would be a show-stopper), etc."
"...supporting TLS (is this a feature? If not this would be a show-stopper), etc."
Boost Beast Translation (zh_Hans)/Doc / Qbk / 08 Design / 4 Faq (qbk) — English
Beast works with the Stream concept, so it automatically works with the `boost::asio::ssl::stream` that you have already set up through Asio.
Beast works with the Stream concept, so it automatically works with the `boost::asio::ssl::stream` that you have already set up through Asio.
Boost Beast Translation (zh_Hans)/Doc / Qbk / 08 Design / 4 Faq (qbk) — English
"There should also be more examples of how to integrate the http service with getting files from the file system, generating responses CGI-style"
"There should also be more examples of how to integrate the http service with getting files from the file system, generating responses CGI-style"
Boost Beast Translation (zh_Hans)/Doc / Qbk / 08 Design / 4 Faq (qbk) — English
The design goal for the library is to not try to invent a web server. We feel that there is a strong need for a basic implementation that models the HTTP message and provides functions to send and receive them over Asio. Such an implementation should serve as a building block upon which higher abstractions such as the aforementioned HTTP service or cgi-gateway can be built.

There are several HTTP servers in the example directory which deliver files, as well as some tested and compiled code snippets which can be used as a starting point for interfacing with other processes.
The design goal for the library is to not try to invent a web server. We feel that there is a strong need for a basic implementation that models the HTTP message and provides functions to send and receive them over Asio. Such an implementation should serve as a building block upon which higher abstractions such as the aforementioned HTTP service or cgi-gateway can be built.

There are several HTTP servers in the example directory which deliver files, as well as some tested and compiled code snippets which can be used as a starting point for interfacing with other processes.
Boost Beast Translation (zh_Hans)/Doc / Qbk / 08 Design / 4 Faq (qbk) — English
"You should send a 100-continue to ask for the rest of the body if required."
"You should send a 100-continue to ask for the rest of the body if required."
Boost Beast Translation (zh_Hans)/Doc / Qbk / 08 Design / 4 Faq (qbk) — English
Deciding on whether to send the "Expect: 100-continue" header or how to handle it on the server side is the caller's responsibility; Beast provides the functionality to send or inspect the header before sending or reading the body.
Deciding on whether to send the "Expect: 100-continue" header or how to handle it on the server side is the caller's responsibility; Beast provides the functionality to send or inspect the header before sending or reading the body.
Boost Beast Translation (zh_Hans)/Doc / Qbk / 08 Design / 4 Faq (qbk) — English
"I would also like to see instances of this library being used in production. That would give some evidence that the design works in practice."
"I would also like to see instances of this library being used in production. That would give some evidence that the design works in practice."
Boost Beast Translation (zh_Hans)/Doc / Qbk / 08 Design / 4 Faq (qbk) — English
Beast has already been on public servers receiving traffic and handling hundreds of millions of dollars' worth of financial transactions daily. The servers run [*rippled], open source software ([@https://github.com/ripple/rippled repository]) implementing the [@https://ripple.com/files/ripple_consensus_whitepaper.pdf [*Ripple Consensus Protocol]], technology provided by [@http://ripple.com Ripple].

Furthermore, the repository has grown significantly in popularity in 2017. There are many users, and some of them participate directly in the repository by reporting issues, performing testing, and in some cases submitting pull requests with code contributions.
Beast has already been on public servers receiving traffic and handling hundreds of millions of dollars' worth of financial transactions daily. The servers run [*rippled], open source software ([@https://github.com/ripple/rippled repository]) implementing the [@https://ripple.com/files/ripple_consensus_whitepaper.pdf [*Ripple Consensus Protocol]], technology provided by [@http://ripple.com Ripple].

Furthermore, the repository has grown significantly in popularity in 2017. There are many users, and some of them participate directly in the repository by reporting issues, performing testing, and in some cases submitting pull requests with code contributions.
Boost Beast Translation (zh_Hans)/Doc / Qbk / 08 Design / 4 Faq (qbk) — English
What about WebSocket message compression?
What about WebSocket message compression?
Boost Beast Translation (zh_Hans)/Doc / Qbk / 08 Design / 4 Faq (qbk) — English
Beast WebSocket supports the permessage-deflate extension described in [@https://tools.ietf.org/html/draft-ietf-hybi-permessage-compression-00 draft-ietf-hybi-permessage-compression-00]. The library comes with a header-only, C++11 port of ZLib's "deflate" codec used in the implementation of the permessage-deflate extension.
Beast WebSocket supports the permessage-deflate extension described in [@https://tools.ietf.org/html/draft-ietf-hybi-permessage-compression-00 draft-ietf-hybi-permessage-compression-00]. The library comes with a header-only, C++11 port of ZLib's "deflate" codec used in the implementation of the permessage-deflate extension.
Boost Beast Translation (zh_Hans)/Doc / Qbk / 08 Design / 4 Faq (qbk) — English
Where is the WebSocket TLS/SSL interface?
Where is the WebSocket TLS/SSL interface?
Boost Beast Translation (zh_Hans)/Doc / Qbk / 08 Design / 4 Faq (qbk) — English
The `websocket::stream` wraps the socket or stream that you provide (for example, a `boost::asio::ip::tcp::socket` or a `boost::asio::ssl::stream`). You establish your TLS connection using the interface on `ssl::stream` like shown in all of the Asio examples, then construct your `websocket::stream` around it.

The WebSocket implementation [*does] provide support for shutting down the TLS connection through the use of the ADL compile-time virtual functions [link beast.ref.boost__beast__websocket__teardown `teardown`] and [link beast.ref.boost__beast__websocket__async_teardown `async_teardown`]. These will properly close the connection as per rfc6455 and overloads are available for TLS streams. Callers may provide their own overloads of these functions for user-defined next layer types.
The `websocket::stream` wraps the socket or stream that you provide (for example, a `boost::asio::ip::tcp::socket` or a `boost::asio::ssl::stream`). You establish your TLS connection using the interface on `ssl::stream` like shown in all of the Asio examples, then construct your `websocket::stream` around it.

The WebSocket implementation [*does] provide support for shutting down the TLS connection through the use of the ADL compile-time virtual functions [link beast.ref.boost__beast__websocket__teardown `teardown`] and [link beast.ref.boost__beast__websocket__async_teardown `async_teardown`]. These will properly close the connection as per rfc6455 and overloads are available for TLS streams. Callers may provide their own overloads of these functions for user-defined next layer types.
Boost Beast Translation (zh_Hans)/Doc / Qbk / 08 Design / 4 Faq (qbk) — English
Windows and OpenSSL: How do I install and build with OpenSSL on Microsoft Windows?
Windows and OpenSSL: How do I install and build with OpenSSL on Microsoft Windows?
Boost Beast Translation (zh_Hans)/Doc / Qbk / 08 Design / 4 Faq (qbk) — English
An easy method is to use command-line package installers chocolatey or scoop. Examples: "choco install -y openssl --x86 --version 1.1.1.700" or "scoop install openssl@1.1.1g -a 32bit -g"

If you've installed OpenSSL to a directory with spaces in the name, it's often preferable to create a symbolic link so that you may use a simpler path, such as:

mklink /D "OpenSSL" "Program Files (x86)\\OpenSSL-Win32"

Set the environment variable OPENSSL_ROOT to the location of the new install:

set OPENSSL_ROOT=C:/OpenSSL

Then, proceed to build. Refer to beast/.dockers/windows-vs-32/Dockerfile for an example of building the test cases with OpenSSL.
An easy method is to use command-line package installers chocolatey or scoop. Examples: "choco install -y openssl --x86 --version 1.1.1.700" or "scoop install openssl@1.1.1g -a 32bit -g"

If you've installed OpenSSL to a directory with spaces in the name, it's often preferable to create a symbolic link so that you may use a simpler path, such as:

mklink /D "OpenSSL" "Program Files (x86)\\OpenSSL-Win32"

Set the environment variable OPENSSL_ROOT to the location of the new install:

set OPENSSL_ROOT=C:/OpenSSL

Then, proceed to build. Refer to beast/.dockers/windows-vs-32/Dockerfile for an example of building the test cases with OpenSSL.
Boost Beast Translation (zh_Hans)/Doc / Qbk / Main (qbk) — English
__new__ indicates a new or updated section in this version.
__new__ indicates a new or updated section in this version.
Boost Beast Translation (zh_Hans)/Doc / Qbk / Main (qbk) — English
__example__ contains example source code.
__example__ contains example source code.
Boost Beast Translation (zh_Hans)/Doc / Qbk / Main (qbk) — English
__video__ contains video presentation content
__video__ contains video presentation content
Boost Beast Translation (zh_Hans)/Doc / Qbk / Main (qbk) — English
Reference
Reference
Boost Beast Translation (zh_Hans)/Doc / Qbk / Main (qbk) — English
__new__ indicates an item that was recently added.
__new__ indicates an item that was recently added.
Boost Beast Translation (zh_Hans)/Doc / Qbk / Main (qbk) — English
This Page Intentionally Left Blank 2/2
This Page Intentionally Left Blank 2/2
Boost Beast Translation (zh_Hans)/Doc / Qbk / Release Notes (qbk) — English
Release Notes
Release Notes
Boost Beast Translation (zh_Hans)/Doc / Qbk / Release Notes (qbk) — English
Boost 1.91
Boost 1.91
Boost Beast Translation (zh_Hans)/Doc / Qbk / Release Notes (qbk) — English
* [issue 3066] Fixed typecast warnings in `inflate_with_eb`
* [issue 3066] Fixed typecast warnings in `inflate_with_eb`
Boost Beast Translation (zh_Hans)/Doc / Qbk / Release Notes (qbk) — English
* [issue 3077] Enforced 8KB sanity limit on chunk headers
* [issue 3085] Made OpenSSL an optional dependency for tests
* [issue 3074] Removed dependency on Boost.StaticAssert
* [issue 3091] Added `HTTP2-Settings` to HTTP field enum
* [issue 3077] Enforced 8KB sanity limit on chunk headers
* [issue 3085] Made OpenSSL an optional dependency for tests
* [issue 3074] Removed dependency on Boost.StaticAssert
* [issue 3091] Added `HTTP2-Settings` to HTTP field enum
Boost Beast Translation (zh_Hans)/Doc / Qbk / Release Notes (qbk) — English
Boost 1.90
Boost 1.90
Boost Beast Translation (zh_Hans)/Doc / Qbk / Release Notes (qbk) — English
* [issue 3042] `http::parser` rejects non-standard trailer fields by default.
* [issue 3042] `http::parser` rejects non-standard trailer fields by default.
Boost Beast Translation (zh_Hans)/Doc / Qbk / Release Notes (qbk) — English
* [issue 3042] `http::basic_parser` uses a dedicated callback for trailer fields.
* [issue 3042] `http::basic_parser` uses a dedicated callback for trailer fields.
Boost Beast Translation (zh_Hans)/Doc / Qbk / Release Notes (qbk) — English
* [issue 3042] `http::field` constants are updated.
* [issue 3042] `http::field` constants are updated.
Boost Beast Translation (zh_Hans)/Doc / Qbk / Release Notes (qbk) — English
* [issue 3034] Fixed allocator move/copy assignment in `flat_buffer` and `multi_buffer`
* [issue 3028] Fixed websocket permessage-deflate error on partial message consumption
* [issue 3032] `http::buffer_body` ignores empty chunks
* [issue 3034] Fixed allocator move/copy assignment in `flat_buffer` and `multi_buffer`
* [issue 3028] Fixed websocket permessage-deflate error on partial message consumption
* [issue 3032] `http::buffer_body` ignores empty chunks
Boost Beast Translation (zh_Hans)/Doc / Qbk / Release Notes (qbk) — English
* [issue 3039] Added `http::basic_fields::contains` member function
* [issue 3050] Removed dependency on Boost.Preprocessor
* [issue 3048] Removed dependency on Boost.StaticAssert
* [issue 3039] Added `http::basic_fields::contains` member function
* [issue 3050] Removed dependency on Boost.Preprocessor
* [issue 3048] Removed dependency on Boost.StaticAssert
Boost Beast Translation (zh_Hans)/Doc / Qbk / Release Notes (qbk) — English
Boost 1.89
Boost 1.89
Boost Beast Translation (zh_Hans)/Doc / Qbk / Release Notes (qbk) — English
* [issue 3002] Conditionally defined `immediate_executor_type` in `async_base`
* [issue 2999] Used `handshake_timeout` for closing handshake during read operations
* [issue 3003] Added missing `cstdint` header to `detail/cpu_info.hpp`
* [issue 3016] Fixed `std::is_trivial` deprecation warnings
* [issue 3019] Fixed `-Wmaybe-uninitialized` warnings
* [issue 3002] Conditionally defined `immediate_executor_type` in `async_base`
* [issue 2999] Used `handshake_timeout` for closing handshake during read operations
* [issue 3003] Added missing `cstdint` header to `detail/cpu_info.hpp`
* [issue 3016] Fixed `std::is_trivial` deprecation warnings
* [issue 3019] Fixed `-Wmaybe-uninitialized` warnings
Boost Beast Translation (zh_Hans)/Doc / Qbk / Release Notes (qbk) — English
* [issue 3005] Replaced `detail/work_guard.hpp` with `net::executor_work_guard`
* [issue 3016] Fixed portability issues for building tests in MinGW
* [issue 3005] Replaced `detail/work_guard.hpp` with `net::executor_work_guard`
* [issue 3016] Fixed portability issues for building tests in MinGW
Boost Beast Translation (zh_Hans)/Doc / Qbk / Release Notes (qbk) — English
* [issue 3009] Removed moved sections from documentation
* [issue 3009] Removed superfluous log messages from tests
* [issue 3009] Removed moved sections from documentation
* [issue 3009] Removed superfluous log messages from tests
Boost Beast Translation (zh_Hans)/Doc / Qbk / Release Notes (qbk) — English
Boost 1.88
Boost 1.88
Boost Beast Translation (zh_Hans)/Doc / Qbk / Release Notes (qbk) — English
* [issue 2962] Fixed out-of-bounds access in `iequals` function
* [issue 2962] Fixed out-of-bounds access in `iequals` function
Boost Beast Translation (zh_Hans)/Doc / Qbk / Release Notes (qbk) — English
* [issue 2974] Updated SSL examples to verify peer certificate hostname
* [issue 2954] Refactored CMakeLists
* [issue 2955] Removed Boost.Scope dependency from examples
* [issue 2716] WebSockets: Peer pings are counted as activity for `idle_timeout`
* [issue 2974] Updated SSL examples to verify peer certificate hostname
* [issue 2954] Refactored CMakeLists
* [issue 2955] Removed Boost.Scope dependency from examples
* [issue 2716] WebSockets: Peer pings are counted as activity for `idle_timeout`
Boost Beast Translation (zh_Hans)/Doc / Qbk / Release Notes (qbk) — English
* [issue 2918] Added new examples for Unix domain sockets
* [issue 2910] Added SSL/TLS Certificate section to documentation
* [issue 2730] Improved documentation of `websocket::stream::async_close`
* [issue 2918] Added new examples for Unix domain sockets
* [issue 2910] Added SSL/TLS Certificate section to documentation
* [issue 2730] Improved documentation of `websocket::stream::async_close`
Boost Beast Translation (zh_Hans)/Doc / Qbk / Release Notes (qbk) — English
Boost 1.87
Boost 1.87
Boost Beast Translation (zh_Hans)/Doc / Qbk / Release Notes (qbk) — English
* [issue 2920] Added `error_code` overload for `basic_fields::insert()`
* [issue 2911] Added overload for `websocket::stream::get_status` to query permessage-deflate status
* [issue 2920] Added `error_code` overload for `basic_fields::insert()`
* [issue 2911] Added overload for `websocket::stream::get_status` to query permessage-deflate status
Boost Beast Translation (zh_Hans)/Doc / Qbk / Release Notes (qbk) — English
* [issue 2926] Fixed use-after-move in calls to `net::dispatch` within `http::basic_stream`, which caused `bad_executor` exceptions on timeouts
* [issue 2915] Removed mutating operations in initiating functions
* [issue 2915] Fixed cancellation handling in `teardown_tcp_op`
* [issue 2920] Set `state_` in `basic_parser` before calling `on_finish_impl`
* [issue 2939] Removed static specifier from `clamp` functions
* [issue 2903] Addressed `-Wattributes` warnings in tests
* [issue 2944] Addressed unreachable code warning in tests
* [issue 2926] Fixed use-after-move in calls to `net::dispatch` within `http::basic_stream`, which caused `bad_executor` exceptions on timeouts
* [issue 2915] Removed mutating operations in initiating functions
* [issue 2915] Fixed cancellation handling in `teardown_tcp_op`
* [issue 2920] Set `state_` in `basic_parser` before calling `on_finish_impl`
* [issue 2939] Removed static specifier from `clamp` functions
* [issue 2903] Addressed `-Wattributes` warnings in tests
* [issue 2944] Addressed unreachable code warning in tests
Boost Beast Translation (zh_Hans)/Doc / Qbk / Release Notes (qbk) — English
* [issue 2940] Added forward declaration headers for types in `beast::http` namespace
* [issue 2920] Enabled `http::parser` to use `basic_fields::insert()` with `error_code` overload
* [issue 2920] Applied `header_limit_` in `http::basic_parser` to trailer headers
* [issue 2920] Improved `http::basic_parser` to return `http::error::header_limit` earlier
* [issue 2905] Added support for modular boost build structure
* [issue 2940] Added forward declaration headers for types in `beast::http` namespace
* [issue 2920] Enabled `http::parser` to use `basic_fields::insert()` with `error_code` overload
* [issue 2920] Applied `header_limit_` in `http::basic_parser` to trailer headers
* [issue 2920] Improved `http::basic_parser` to return `http::error::header_limit` earlier
* [issue 2905] Added support for modular boost build structure
Boost Beast Translation (zh_Hans)/Doc / Qbk / Release Notes (qbk) — English
Boost 1.86
Boost 1.86
Boost Beast Translation (zh_Hans)/Doc / Qbk / Release Notes (qbk) — English
* [issue 2878] Added HTTP status code *418 I'm a teapot*
* [issue 2878] Added HTTP status code *418 I'm a teapot*
Boost Beast Translation (zh_Hans)/Doc / Qbk / Release Notes (qbk) — English
* [issue 2879] Narrowing conversion in `read_size_hint_db()`
* [issue 2893] Overloads that are ambiguous when using default completion tokens
* [issue 2517] Misplaced static_assert in `http::basic_fields` move-assignment operator
* [issue 2880] Underflow of `bytes_transferred` in WebSocket partial write operations
* [issue 2879] `websocket::stream::read_size_hint()` does not exceed `read_message_max`
* [issue 2877] Various warnings in tests
* [issue 2872] Error handling in SSL shutdown operations in examples
* [issue 2869] Annotate fallthrough case in zlib
* [issue 2866] Handling of expired timers in `basic_stream::ops::transfer_op`
* [issue 2864] Ambiguity in `test::basic_stream` constructor overloads
* [issue 2861] Partial parsing of the final chunk in `http::parser`
* [issue 2879] Narrowing conversion in `read_size_hint_db()`
* [issue 2893] Overloads that are ambiguous when using default completion tokens
* [issue 2517] Misplaced static_assert in `http::basic_fields` move-assignment operator
* [issue 2880] Underflow of `bytes_transferred` in WebSocket partial write operations
* [issue 2879] `websocket::stream::read_size_hint()` does not exceed `read_message_max`
* [issue 2877] Various warnings in tests
* [issue 2872] Error handling in SSL shutdown operations in examples
* [issue 2869] Annotate fallthrough case in zlib
* [issue 2866] Handling of expired timers in `basic_stream::ops::transfer_op`
* [issue 2864] Ambiguity in `test::basic_stream` constructor overloads
* [issue 2861] Partial parsing of the final chunk in `http::parser`
Boost Beast Translation (zh_Hans)/Doc / Qbk / Release Notes (qbk) — English
* [issue 2897] Graceful shutdown in `server_flex_awaitable` example
* [issue 2897] Simplified awaitable examples
* [issue 2888] Added fuzzing targets
* [issue 2875] Removed superfluous uses of `std::bind` in some examples
* [issue 2875] `ssl_stream` does not use `flat_stream`
* [issue 2897] Graceful shutdown in `server_flex_awaitable` example
* [issue 2897] Simplified awaitable examples
* [issue 2888] Added fuzzing targets
* [issue 2875] Removed superfluous uses of `std::bind` in some examples
* [issue 2875] `ssl_stream` does not use `flat_stream`
Boost Beast Translation (zh_Hans)/Doc / Qbk / Release Notes (qbk) — English
* [issue 2875] `ssl_stream` and `flat_stream` marked as deprecated
* [issue 2875] `net::ssl::stream` is canonical in snippets and examples
* [issue 2872] Added `SSL/TLS Shutdown Procedure` section
* [issue 2875] `ssl_stream` and `flat_stream` marked as deprecated
* [issue 2875] `net::ssl::stream` is canonical in snippets and examples
* [issue 2872] Added `SSL/TLS Shutdown Procedure` section
Boost Beast Translation (zh_Hans)/Doc / Qbk / Release Notes (qbk) — English
Boost 1.85
Boost 1.85
Boost Beast Translation (zh_Hans)/Doc / Qbk / Release Notes (qbk) — English
* [issue 2811] The status code list has been updated to conform with the IANA registry
* [issue 2811] The status code list has been updated to conform with the IANA registry
Boost Beast Translation (zh_Hans)/Doc / Qbk / Release Notes (qbk) — English
* [issue 2803] Unreachable code warning in `buffers_cat.hpp`
* [issue 2778] Connection error handling in `websocker_server_awaitable` example
* [issue 2739] Concurrent calls to `async_write` in advanced server examples
* [issue 2810] zlib name conflicts with minizip
* [issue 2818] host string should be updated after `SSL_set_tlsext_host_name()`
* [issue 2803] Unreachable code warning in `buffers_cat.hpp`
* [issue 2778] Connection error handling in `websocker_server_awaitable` example
* [issue 2739] Concurrent calls to `async_write` in advanced server examples
* [issue 2810] zlib name conflicts with minizip
* [issue 2818] host string should be updated after `SSL_set_tlsext_host_name()`
Boost Beast Translation (zh_Hans)/Doc / Qbk / Release Notes (qbk) — English
* [issue 2782] `asio::associator` is specialized for `bind_wrapper` and `bind_front_wrapper`
* [issue 2646] Add non-allocating overload for error category message function
* [issue 2782] `asio::associator` is specialized for `bind_wrapper` and `bind_front_wrapper`
* [issue 2646] Add non-allocating overload for error category message function
Boost Beast Translation (zh_Hans)/Doc / Qbk / Release Notes (qbk) — English
* [issue 2789] Specifies when calling `http::message::prepare_payload()` is optional
* [issue 2799] Operations affected by `basic_stream::expires_after()`
* [issue 2808] `teardown()` and `async_teardown()` are customization points
* [issue 2814] Moving or copying `http::serializer` after first usage is undefined behaviour
* [issue 2817] `websocket::permessage_deflate` should be configured before performing the WebSocket handshake
* [issue 2816] `bytes_transferred` in http reads operations reports the number of bytes consumed by the HTTP parser
* [issue 2789] Specifies when calling `http::message::prepare_payload()` is optional
* [issue 2799] Operations affected by `basic_stream::expires_after()`
* [issue 2808] `teardown()` and `async_teardown()` are customization points
* [issue 2814] Moving or copying `http::serializer` after first usage is undefined behaviour
* [issue 2817] `websocket::permessage_deflate` should be configured before performing the WebSocket handshake
* [issue 2816] `bytes_transferred` in http reads operations reports the number of bytes consumed by the HTTP parser
Boost Beast Translation (zh_Hans)/Doc / Qbk / Release Notes (qbk) — English
Boost 1.84
Boost 1.84
Boost Beast Translation (zh_Hans)/Doc / Qbk / Release Notes (qbk) — English
* Remove deprecated allocation and invocation hooks
* Remove deprecated allocation and invocation hooks
Boost Beast Translation (zh_Hans)/Doc / Qbk / Release Notes (qbk) — English
* Support for `immediate_executor`
* Support for `immediate_executor`
Boost Beast Translation (zh_Hans)/Doc / Qbk / Release Notes (qbk) — English
* [issue 2766] Use the explicit type std::size_t when completing transfer_op
* [issue 2727] Replaced `BOOST_ASIO_INITFN_RESULT_TYPE` with `BOOST_ASIO_INITFN_AUTO_RES`
* [issue 2715] `server-flex-awaitable` example resets parser
* [issue 2766] Use the explicit type std::size_t when completing transfer_op
* [issue 2727] Replaced `BOOST_ASIO_INITFN_RESULT_TYPE` with `BOOST_ASIO_INITFN_AUTO_RES`
* [issue 2715] `server-flex-awaitable` example resets parser
Boost Beast Translation (zh_Hans)/Doc / Qbk / Release Notes (qbk) — English
* [issue 2713] Corrected the `websocket::stream::async_ping/pong` handler requirement
* [issue 2755] Update documentation for `websocket::stream::async_write_some`
* [issue 2713] Corrected the `websocket::stream::async_ping/pong` handler requirement
* [issue 2755] Update documentation for `websocket::stream::async_write_some`
Boost Beast Translation (zh_Hans)/Doc / Qbk / Release Notes (qbk) — English
Boost 1.83
Boost 1.83
Boost Beast Translation (zh_Hans)/Doc / Qbk / Release Notes (qbk) — English
* [issue 2680] aligned_storage unused for C+23
* [issue 2653] MSVC literal `not` error
* [issue 2661] ssl_stream ambiguity error on clang
* [issue 2649] Jamefile uses openssl.jam
* [issue 2680] aligned_storage unused for C+23
* [issue 2653] MSVC literal `not` error
* [issue 2661] ssl_stream ambiguity error on clang
* [issue 2649] Jamefile uses openssl.jam
Boost Beast Translation (zh_Hans)/Doc / Qbk / Release Notes (qbk) — English
Boost 1.82
Boost 1.82
Boost Beast Translation (zh_Hans)/Doc / Qbk / Release Notes (qbk) — English
* [issue 2475] Add `error_code`s use source_location
* [issue 2475] Add `error_code`s use source_location
Boost Beast Translation (zh_Hans)/Doc / Qbk / Release Notes (qbk) — English
* [issue 2602] tcp_stream uses the correct executor of the timer.
* [issue 2638] `std::placeholders` ambiguity fix.
* [issue 2602] tcp_stream uses the correct executor of the timer.
* [issue 2638] `std::placeholders` ambiguity fix.
Boost Beast Translation (zh_Hans)/Doc / Qbk / Release Notes (qbk) — English
* error_categories use numeric ids
* `file_body` support seek
* error_categories use numeric ids
* `file_body` support seek
Boost Beast Translation (zh_Hans)/Doc / Qbk / Release Notes (qbk) — English
Boost 1.81
Boost 1.81
Boost Beast Translation (zh_Hans)/Doc / Qbk / Release Notes (qbk) — English
* Add `buffers_generator`
* Add [link beast.ref.boost__beast__http__message_generator `http::message_generator`]
* Add [link beast.ref.boost__beast__buffer_ref `buffer_ref`]
* Support for per-operation cancellation
* Add `buffers_generator`
* Add [link beast.ref.boost__beast__http__message_generator `http::message_generator`]
* Add [link beast.ref.boost__beast__buffer_ref `buffer_ref`]
* Support for per-operation cancellation
Boost Beast Translation (zh_Hans)/Doc / Qbk / Release Notes (qbk) — English
* [issue 2439] Fix CVE-2018-25032 in zlib streams
* [issue 264] Websocket support continue in upgrade
* [issue 471] Unquote takes s by reference
* [issue 2439] Fix CVE-2018-25032 in zlib streams
* [issue 264] Websocket support continue in upgrade
* [issue 471] Unquote takes s by reference
Boost Beast Translation (zh_Hans)/Doc / Qbk / Release Notes (qbk) — English
* [issue 2104] C++20 awaitable examples.
* [issue 226], [issue 227] per-message compression options
* [issue 2449] websocket timeout option api
* [issue 2468] multiple content length error
* [issue 2104] C++20 awaitable examples.
* [issue 226], [issue 227] per-message compression options
* [issue 2449] websocket timeout option api
* [issue 2468] multiple content length error
Boost Beast Translation (zh_Hans)/Doc / Qbk / Release Notes (qbk) — English
* Use `span` from Boost.Core
* Use `static_string` from Boost.StaticString
* `serializer::is_done` is `const`
* Support for default-completion and rebind
* [issue 2469] s390x architecture support
* Use `span` from Boost.Core
* Use `static_string` from Boost.StaticString
* `serializer::is_done` is `const`
* Support for default-completion and rebind
* [issue 2469] s390x architecture support
Boost Beast Translation (zh_Hans)/Doc / Qbk / Release Notes (qbk) — English
* [issue 891] Feature table for buffers
* [issue 516] Case-insensitivity for fields is stated
* [issue 298] api version is documented
* [issue 891] Feature table for buffers
* [issue 516] Case-insensitivity for fields is stated
* [issue 298] api version is documented
Boost Beast Translation (zh_Hans)/Doc / Qbk / Release Notes (qbk) — English
Boost 1.80
Boost 1.80
Boost Beast Translation (zh_Hans)/Doc / Qbk / Release Notes (qbk) — English
* [issue 2363] Remove `BOOST_BEAST_USE_STD_STRING_VIEW`
* [issue 2417] use boost::core::string_view. This improves inter-conversion between string_view implementations. Some observable differences for users:
* [issue 2363] Remove `BOOST_BEAST_USE_STD_STRING_VIEW`
* [issue 2417] use boost::core::string_view. This improves inter-conversion between string_view implementations. Some observable differences for users:
Boost Beast Translation (zh_Hans)/Doc / Qbk / Release Notes (qbk) — English
Boost 1.79
Boost 1.79
Boost Beast Translation (zh_Hans)/Doc / Qbk / Release Notes (qbk) — English
* [issue 2391] Add missing include for file_body test.
* [issue 2364] Fix WebSocket handshake response on failure.
* [issue 2280] (related) Fix open append mode for file_posix.
* [issue 2280] Fix open append mode for file_win32.
* [issue 2280] Fix file open with append/append_existing flag on Windows
* [issue 2354] Fix clang-cl UTF8 path handling for `file_win32`.
* [issue 2354] Fix clang-cl UTF8 path handling for `file_stdio`.
* [issue 2391] Add missing include for file_body test.
* [issue 2364] Fix WebSocket handshake response on failure.
* [issue 2280] (related) Fix open append mode for file_posix.
* [issue 2280] Fix open append mode for file_win32.
* [issue 2280] Fix file open with append/append_existing flag on Windows
* [issue 2354] Fix clang-cl UTF8 path handling for `file_win32`.
* [issue 2354] Fix clang-cl UTF8 path handling for `file_stdio`.
Boost Beast Translation (zh_Hans)/Doc / Qbk / Release Notes (qbk) — English
* [issue 2375] Add ARM64 builds to drone CI
* [issue 2217] Fix async_base documentation link
* [issue 2280] Add tests for file open in append/append_existing mode
* [issue 2351] Update CI to include gcc 11, clang 12, msvc 14.3
* [issue 2350] Add individual tests to CMake workflow
* [issue 2375] Add ARM64 builds to drone CI
* [issue 2217] Fix async_base documentation link
* [issue 2280] Add tests for file open in append/append_existing mode
* [issue 2351] Update CI to include gcc 11, clang 12, msvc 14.3
* [issue 2350] Add individual tests to CMake workflow
Boost Beast Translation (zh_Hans)/Doc / Qbk / Release Notes (qbk) — English
Boost 1.78
Boost 1.78
Boost Beast Translation (zh_Hans)/Doc / Qbk / Release Notes (qbk) — English
* Fix CVE-2016-9840 in zlib implementation.
* Fix TLS SNI handling in websocket_client_async_ssl example.
* [issue 2313] Fix reuse of sliding window in WebSocket permessage_deflate.
* Fix accept error handling in http_server_async example.
* Fix CVE-2016-9840 in zlib implementation.
* Fix TLS SNI handling in websocket_client_async_ssl example.
* [issue 2313] Fix reuse of sliding window in WebSocket permessage_deflate.
* Fix accept error handling in http_server_async example.
Boost Beast Translation (zh_Hans)/Doc / Qbk / Release Notes (qbk) — English
* Remove test framework's dependency on RTTI.
* Move library-specific docca configuration to Beast.
* Remove dependency on RTTI in `test::stream`.
* Fix missing includes in test headers.
* Remove test framework's dependency on RTTI.
* Move library-specific docca configuration to Beast.
* Remove dependency on RTTI in `test::stream`.
* Fix missing includes in test headers.
Boost Beast Translation (zh_Hans)/Doc / Qbk / Release Notes (qbk) — English
Boost 1.77
Boost 1.77
Boost Beast Translation (zh_Hans)/Doc / Qbk / Release Notes (qbk) — English
* [issue 2233] Remove use of POSIX-only constant.
* [issue 2233] Remove use of POSIX-only constant.
Boost Beast Translation (zh_Hans)/Doc / Qbk / Release Notes (qbk) — English
* Fixes to tests.
* Improvements and fixes in Github and Drone CI.
* Accommodate Docca updates.
* Update example root certificates.
* Add example of reading large response body.
* Remove Travis CI.
* Update CMakeLists.txt
* Fixes to tests.
* Improvements and fixes in Github and Drone CI.
* Accommodate Docca updates.
* Update example root certificates.
* Add example of reading large response body.
* Remove Travis CI.
* Update CMakeLists.txt
Boost Beast Translation (zh_Hans)/Doc / Qbk / Release Notes (qbk) — English
Boost 1.76
Boost 1.76
Boost Beast Translation (zh_Hans)/Doc / Qbk / Release Notes (qbk) — English
* [issue 2139] Add executor rebind to test::stream.
* Fix unused variable compiler warning in WebSocket async shutdown.
* [issue 2139] Add executor rebind to test::stream.
* Fix unused variable compiler warning in WebSocket async shutdown.
Boost Beast Translation (zh_Hans)/Doc / Qbk / Release Notes (qbk) — English
* [issue 2124] Floating point support no longer required to use Beast.
* Reduce size of websockety compiled code by using a common buffers type for all operations.
* HTTP Parser has improved detection of incorrect use.
* [issue 2124] Floating point support no longer required to use Beast.
* Reduce size of websockety compiled code by using a common buffers type for all operations.
* HTTP Parser has improved detection of incorrect use.
Boost Beast Translation (zh_Hans)/Doc / Qbk / Release Notes (qbk) — English
* [issue 2140] Add cxxstd tag to library metadata.
* Move to Drone CI.
* Minor documentation formatting improvements.
* CML now finds required Boost::thread library during in-tree build.
* [issue 2140] Add cxxstd tag to library metadata.
* Move to Drone CI.
* Minor documentation formatting improvements.
* CML now finds required Boost::thread library during in-tree build.
Boost Beast Translation (zh_Hans)/Doc / Qbk / Release Notes (qbk) — English
Boost 1.75
Boost 1.75
Boost Beast Translation (zh_Hans)/Doc / Qbk / Release Notes (qbk) — English
* Eliminate spurious unused parameter warning in `detect_ssl`.
* Update Websocket examples to set the SNI for TLS connections.
* [issue 2023] websocket async_shutdown will now shutdown the underlying TLS transport.
* [issue 2011] File open with append_existing flag now works correctly in posix environments.
* [issue 2039] Windows builds now link to bcrypt as required by the filesystem library.
* [issue 2063] Logic error fixed in `advanced_server_flex` example.
* [issue 1582] Fix unreachable code error on MSVC.
* [issue 2070] Fix http body behaviour when body_limit it none.
* [issue 2065] Fix behaviour of `basic_stream` when a zero-length write is requested.
* [issue 2080] Add enums representing Sec-* HTTP headers.
* [issue 2085] Fix `nullptr` implicit cast on `fields::set()`.
* [issue 2029] Fix C++20 tests for `basic_stream`.
* Eliminate spurious unused parameter warning in `detect_ssl`.
* Update Websocket examples to set the SNI for TLS connections.
* [issue 2023] websocket async_shutdown will now shutdown the underlying TLS transport.
* [issue 2011] File open with append_existing flag now works correctly in posix environments.
* [issue 2039] Windows builds now link to bcrypt as required by the filesystem library.
* [issue 2063] Logic error fixed in `advanced_server_flex` example.
* [issue 1582] Fix unreachable code error on MSVC.
* [issue 2070] Fix http body behaviour when body_limit it none.
* [issue 2065] Fix behaviour of `basic_stream` when a zero-length write is requested.
* [issue 2080] Add enums representing Sec-* HTTP headers.
* [issue 2085] Fix `nullptr` implicit cast on `fields::set()`.
* [issue 2029] Fix C++20 tests for `basic_stream`.
Boost Beast Translation (zh_Hans)/Doc / Qbk / Release Notes (qbk) — English
* Add handler tracking to asynchronous operations:
* Add handler tracking to asynchronous operations:
Boost Beast Translation (zh_Hans)/Doc / Qbk / Release Notes (qbk) — English
* Add Bishop-Fox 2020 Security Assessment.
* Add Bishop-Fox 2020 Security Assessment.
Boost Beast Translation (zh_Hans)/Doc / Qbk / Release Notes (qbk) — English
Boost 1.74
Boost 1.74