[FOLD]

Author: vinniefalco

doc/modules/ROOT/pages/1.intro.adoc

@@ -62,13 +62,20 @@ appropriate action to ensure RFC compliance:
 [literal]
 https://tools.ietf.org/html/rfc7230#section-6.1[*Connection*]
 https://tools.ietf.org/html/rfc7230#appendix-A.1.2[*Proxy-Connection*]
-|
+|This field lets the sender specify control options for the current connection.
+Typical values include close, keep-alive, and upgrade.
 
 |https://tools.ietf.org/html/rfc7230#section-3.3.2[*Content-Length*]
-|
+|When present, this field tells the recipient the exact size of the message
+body, measured in bytes, that follows the header.
 
 |https://tools.ietf.org/html/rfc7230#section-3.3.1[*Transfer-Encoding*]
-|
+|This optional field specifies the sequence of transfer codings that have been,
+or will be, applied to the content payload to produce the message body.
+
+The library supports the chunked, gzip, deflate, and brotli encoding schemes,
+in any valid combination. Encodings can be automatically applied or removed
+as needed by the caller.
 
 |https://tools.ietf.org/html/rfc7230#section-6.7[*Upgrade]
 |