boostorg/beast
1
0
Fork 1
mirror of https://github.com/boostorg/beast.git synced 2025-07-30 04:47:29 +02:00
Code Issues Packages Projects Releases Wiki Activity

Fix typos

Browse Source
This commit is contained in:
Denis Glazachev
2019-03-30 20:50:29 +04:00
committed by Vinnie Falco
parent 8ec1a4d90f
commit 6dba0d0be8
1 changed files with 2 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
doc/qbk/05_http_examples/_http_examples.qbk
View File

@ -39,7 +39,7 @@ type depending on the method verb:
The Expect field with the value "100-continue" in a request is special. It The Expect field with the value "100-continue" in a request is special. It
indicates that the after sending the message header, a client desires an indicates that the after sending the message header, a client desires an
immediate informational response before sending the the message body, which immediate informational response before sending the message body, which
presumably may be expensive to compute or large. This behavior is described in presumably may be expensive to compute or large. This behavior is described in
[@https://tools.ietf.org/html/rfc7231#section-5.1.1 rfc7231 section 5.1.1]. [@https://tools.ietf.org/html/rfc7231#section-5.1.1 rfc7231 section 5.1.1].
Invoking the 100-continue behavior is implemented easily in a client by Invoking the 100-continue behavior is implemented easily in a client by
@ -58,7 +58,7 @@ this client action looks like this:
The Expect field with the value "100-continue" in a request is special. It The Expect field with the value "100-continue" in a request is special. It
indicates that the after sending the message header, a client desires an indicates that the after sending the message header, a client desires an
immediate informational response before sending the the message body, which immediate informational response before sending the message body, which
presumably may be expensive to compute or large. This behavior is described in presumably may be expensive to compute or large. This behavior is described in
[@https://tools.ietf.org/html/rfc7231#section-5.1.1 rfc7231 section 5.1.1]. [@https://tools.ietf.org/html/rfc7231#section-5.1.1 rfc7231 section 5.1.1].
Handling the Expect field can be implemented easily in a server by constructing Handling the Expect field can be implemented easily in a server by constructing