Exit Zen
1
string ID 10
type: section title
English
WebSocket (Autobahn|Testsuite)
30/300 · 30
1
string ID 12
type: section title
English
HTTP Message Container __video__
32/320 · 32
1
string ID 10
type: section title
English
Security Review (Bishop Fox) __video__
38/380 · 38
1
string ID 10
type: section title
English
Writing Composed Operations
27/270 · 27
1
string ID 10
type: section title
English
Echo __example__
16/160 · 16
1
string ID 10
type: section title
English
Configuration Preprocessor Definitions
38/380 · 38
1
string ID 10
type: section title
English
Layered Streams
15/150 · 15
2
string ID 12
type: paragraph
English
For message payloads whose size is not known ahead of time, HTTP version 1.1 defines the [@https://tools.ietf.org/html/rfc7230#section-4.1 ['chunked]] transfer coding. This coding consists of zero or more [@https://tools.ietf.org/html/rfc7230#section-4.1 ['chunked bodies]], followed by a [@https://tools.ietf.org/html/rfc7230#section-4.1 ['last chunk]]. Each chunked body may contain optional application-defined, connection-specific [@https://tools.ietf.org/html/rfc7230#section-4.1.1 ['chunk-extensions]]. The last chunk may contain additional HTTP field values in a section of the last chunk called a [@https://tools.ietf.org/html/rfc7230#section-4.1.2 ['chunk-trailer]]. The field values are "promised" in the header as a comma delimited list of field names in the [@https://tools.ietf.org/html/rfc7230#section-4.4 [*Trailer]] field value. Clients indicate their willingness to accept trailers by including the "trailers" token in the [@https://tools.ietf.org/html/rfc7230#section-4.3 [*TE]] field value.
1009/10090 · 1009
2
string ID 13
type: paragraph
English
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.
617/6170 · 617
2
string ID 12
type: paragraph
English
In this example we will build a simple function to detect the presence of the [@https://tools.ietf.org/html/rfc2246#section-7.4 TLS client handshake] given an input buffer sequence. Then we build on the example by adding a synchronous stream algorithm. Finally, we implement an asynchronous detection function using a composed operation. This SSL detector may be used to allow a server to accept both TLS and plain (unencrypted) connections at the same port.
458/4580 · 458
2
string ID 13
type: paragraph
English
Source code and build scripts for these programs are located in the [path_link example example] directory.
106/1060 · 106
2
string ID 172
type: paragraph
English
__example__ contains example source code.
41/410 · 41
2
string ID 14
type: paragraph
English
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:
459/4590 · 459
2
string ID 12
type: paragraph
English
Beast provides synchronous and asynchronous algorithms to parse and serialize HTTP/1 wire format messages on streams. These functions form the message-oriented stream interface:
177/1770 · 177
2
string ID 12
type: paragraph
English
The HTTP protocol defines the [@https://tools.ietf.org/html/rfc7230#section-2.1 client and server roles]: clients send requests and servers send back responses. When a client and server have established a connection, the client sends a series of requests while the server sends back at least one response for each received request in the order those requests were received.
373/3730 · 373
2
string ID 12
type: paragraph
English
To use Beast effectively, a prior understanding of Networking is required. This section reviews these concepts as a reminder and guide for further learning.
156/1560 · 156
2
string ID 13
type: paragraph
English
An instance of __serializer__ can be invoked directly, without using the provided stream operations. This could be useful for implementing algorithms on objects whose interface does not conform to __Stream__. For example, a [@https://github.com/libuv/libuv *libuv* socket]. The serializer interface is interactive; the caller invokes it repeatedly to produce buffers until all of the serialized octets have been generated. Then the serializer is destroyed.
456/4560 · 456
2
string ID 13
type: paragraph
English
Higher level functions such as Basic
36/360 · 36
2
string ID 12
type: paragraph
English
Beast provides a single class template __message__ and some aliases which model HTTP/1 and [@https://tools.ietf.org/html/rfc7540 HTTP/2] messages:
146/1460 · 146
2
string ID 12
type: paragraph
English
Non-trivial algorithms need to do more than receive entire messages at once, such as:
85/850 · 85