Exit Zen
4
string ID 28
type: paragraph
English
The parser provides a few options which may be set before parsing begins:
73/730 · 73
30
string ID 30
type: table title
English
Parser Options
14/140 · 14
6
string ID 30
type: table cell
English
Name
4/100 · 4
7
string ID 30
type: table cell
English
Default
7/100 · 7
8
string ID 30
type: table cell
English
Description
11/110 · 11
9
string ID 30
type: table cell
English
[link beast.ref.boost__beast__http__basic_parser.eager.overload2 `eager`]
73/730 · 73
30
string ID 30
type: table cell
English
`false`
0/100 · 7
11
string ID 30
type: table cell
English
Normally the parser returns after successfully parsing a structured element (header, chunk header, or chunk body) even if there are octets remaining in the input. This is necessary when attempting to parse the header first, or when the caller wants to inspect information which may be invalidated by subsequent parsing, such as a chunk extension. The `eager` option controls whether the parser keeps going after parsing structured element if there are octets remaining in the buffer and no error occurs. This option is automatically set or cleared during certain stream operations to improve performance with no change in functionality.
636/6360 · 636
12
string ID 30
type: table cell
English
[link beast.ref.boost__beast__http__basic_parser.skip.overload2 `skip`]
71/710 · 71
13
string ID 30
type: table cell
English
This option controls whether or not the parser expects to see an HTTP body, regardless of the presence or absence of certain fields such as Content-Length or a chunked Transfer-Encoding. Depending on the request, some responses do not carry a body. For example, a 200 response to a [@https://tools.ietf.org/html/rfc7231#section-4.3.6 CONNECT] request from a tunneling proxy, or a response to a [@https://tools.ietf.org/html/rfc7231#section-4.3.2 HEAD] request. In these cases, callers may use this function inform the parser that no body is expected. The parser will consider the message complete after the header has been received.
632/6320 · 632
14
string ID 30
type: table cell
English
[link beast.ref.boost__beast__http__basic_parser.body_limit `body_limit`]
73/730 · 73
15
string ID 30
type: table cell
English
1MB/8MB
7/100 · 7
16
string ID 30
type: table cell
English
This function sets the maximum allowed size of the content body. When a body larger than the specified size is detected, an error is generated and parsing terminates. This setting helps protect servers from resource exhaustion attacks. The default limit when parsing requests is 1MB, and for parsing responses 8MB.
314/3140 · 314
17
string ID 30
type: table cell
English
[link beast.ref.boost__beast__http__basic_parser.header_limit `header_limit`]
77/770 · 77
18
string ID 30
type: table cell
English
8KB
3/100 · 3
19
string ID 30
type: table cell
English
This function sets the maximum allowed size of the header including all field name, value, and delimiter characters and also including the CRLF sequences in the serialized input.
178/1780 · 178
20
string ID 88
type: section title
English
Read From std::istream __example__
34/340 · 34
21
string ID 90
type: paragraph
English
The standard library provides the type `std::istream` for performing high level read operations on character streams. The variable `std::cin` is based on this input stream. This example uses the buffer oriented interface of __basic_parser__ to build a stream operation which parses an HTTP message from a `std::istream`:
320/3200 · 320
22
string ID 99
type: paragraph
English
Parsing from a `std::istream` could be implemented using an alternate
69/690 · 69
The translation has come to an end.