[FOLD]

Author: vinniefalco

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

@@ -12,7 +12,7 @@
 HTTP is a stream-oriented protocol between two connected programs: one acting
 as the client, the other as the server. While the connection is open, the client
 sends an HTTP request, which the server reads and answers with an HTTP response.
-Requests and responses are paired in order; each request has exactly one
+These _messages_ are paired in order; each request has exactly one
 corresponding response. This exchange of structured messages continues until
 either peer closes the connection, whether normally or due to an error.
 
@@ -50,6 +50,30 @@ Hello, world!
 
 |===
 
+More formally, the ABNF for messages is specified thusly:
+
+[cols="1a,4a"]
+|===
+|Name|ABNF
+
+|message
+|[literal]
+HTTP-message   = request-line / status-line
+                 *( header-field CRLF )
+                 CRLF
+                 [ message-body ]
+
+|request-line
+|[literal]
+request-line   = method SP request-target SP HTTP-version CRLF
+
+|status-line
+|[literal]
+status-line    = HTTP-version SP status-code SP reason-phrase CRLF
+
+|===
+
+
 Most HTTP header field values are domain-specific or application-defined, while
 certain fields commonly recur. The library understands these fields and takes
 appropriate action to ensure RFC compliance:
@@ -58,8 +82,7 @@ appropriate action to ensure RFC compliance:
 |===
 |Field|Description
 
-|
-[literal]
+|[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.
@@ -77,7 +100,7 @@ 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]
+|https://tools.ietf.org/html/rfc7230#section-6.7[*Upgrade*]
 |
 
 |===