The translation has come to an end.
Exit Zen
20
string ID 16
type: variablelist cell
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.
467/4670 · 467
21
string ID 16
type: variablelist cell
English
"...supporting TLS (is this a feature? If not this would be a show-stopper), etc."
82/820 · 82
22
string ID 16
type: variablelist cell
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.
141/1410 · 141
23
string ID 16
type: variablelist cell
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"
145/1450 · 145
24
string ID 16
type: variablelist cell
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.
580/5800 · 580
25
string ID 16
type: variablelist cell
English
"You should send a 100-continue to ask for the rest of the body if required."
77/770 · 77
26
string ID 16
type: variablelist cell
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.
231/2310 · 231
27
string ID 16
type: variablelist cell
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."
143/1430 · 143
28
string ID 16
type: variablelist cell
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.
664/6640 · 664
29
string ID 16
type: variablelist cell
English
What about WebSocket message compression?
41/410 · 41
30
string ID 16
type: variablelist cell
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.
325/3250 · 325
31
string ID 16
type: variablelist cell
English
Where is the WebSocket TLS/SSL interface?
41/410 · 41
32
string ID 16
type: variablelist cell
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.
795/7950 · 795
33
string ID 16
type: variablelist cell
English
Windows and OpenSSL: How do I install and build with OpenSSL on Microsoft Windows?
82/820 · 82
34
string ID 16
type: variablelist cell
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.
644/6440 · 644
The translation has come to an end.