Add exact HTTP request code blocks to all 101 glossary pages

Each test's "What it sends" section now shows the exact wire-format
request sent by the probe, with visible \r\n markers, hex escapes
for control/NUL bytes, and truncated representations for oversized
payloads.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

Author: MDA2AV

docs/content/docs/content-length/cl-non-numeric.md

@@ -16,6 +16,14 @@ weight: 1
 
 A request with a non-numeric `Content-Length` value, e.g., `Content-Length: abc`.
 
+```http
+POST / HTTP/1.1\r\n
+Host: localhost:8080\r\n
+Content-Length: abc\r\n
+\r\n
+```
+
+
 ## What the RFC says
 
 Content-Length is defined as `1*DIGIT`. A value containing non-digit characters does not match this grammar.

docs/content/docs/content-length/cl-plus-sign.md

@@ -16,6 +16,15 @@ weight: 2
 
 A request with a plus sign in the Content-Length value: `Content-Length: +42`.
 
+```http
+POST / HTTP/1.1\r\n
+Host: localhost:8080\r\n
+Content-Length: +5\r\n
+\r\n
+hello
+```
+
+
 ## What the RFC says
 
 The `+` character is not in the DIGIT set (`%x30-39`), so `+42` does not match `1*DIGIT`. This is an invalid Content-Length and MUST be treated as an unrecoverable error.

docs/content/docs/headers/empty-header-name.md

@@ -16,6 +16,16 @@ weight: 3
 
 A header line starting with a colon — effectively an empty field name: `: value`.
 
+```http
+GET / HTTP/1.1\r\n
+Host: localhost:8080\r\n
+: empty-name\r\n
+\r\n
+```
+
+A header line starting with `:` — the header name is empty.
+
+
 ## What the RFC says
 
 Field names are defined as `token = 1*tchar`, requiring at least one valid token character. An empty string does not match `1*tchar`. While there is no explicit "MUST reject empty field names with 400" statement, a line starting with `:` fails to match the `field-line` grammar entirely.

docs/content/docs/headers/expect-unknown.md

@@ -16,6 +16,16 @@ weight: 7
 
 `Expect: 200-ok` — an Expect header with a value the server cannot fulfill.
 
+```http
+GET / HTTP/1.1\r\n
+Host: localhost:8080\r\n
+Expect: 200-ok\r\n
+\r\n
+```
+
+The `Expect` header contains an unknown expectation value (not `100-continue`).
+
+
 ## What the RFC says
 
 > "A server that receives an Expect field value containing a member other than 100-continue MAY respond with a 417 (Expectation Failed) status code to indicate that the unexpected expectation cannot be met." — RFC 9110 Section 10.1.1

docs/content/docs/headers/header-no-colon.md

@@ -16,6 +16,16 @@ weight: 5
 
 A header line with no colon: `InvalidHeaderNoColon`.
 
+```http
+GET / HTTP/1.1\r\n
+Host: localhost:8080\r\n
+NoColonHere\r\n
+\r\n
+```
+
+A header line without any colon separator.
+
+
 ## What the RFC says
 
 The field-line grammar is `field-name ":" OWS field-value OWS`. A line without a colon does not match this grammar. It could be misinterpreted as a continuation line, a new request, or garbage — any of which is dangerous.

docs/content/docs/headers/invalid-header-name.md

@@ -16,6 +16,16 @@ weight: 4
 
 A header with non-token characters in the field name (e.g., characters outside the `tchar` set defined in RFC 9110 Section 5.6.2).
 
+```http
+GET / HTTP/1.1\r\n
+Host: localhost:8080\r\n
+Bad[Name: value\r\n
+\r\n
+```
+
+The header name contains `[` which is not a valid token character.
+
+
 ## What the RFC says
 
 The `tchar` set is: `"!" / "#" / "$" / "%" / "&" / "'" / "*" / "+" / "-" / "." / "^" / "_" / "`" / "|" / "~" / DIGIT / ALPHA`. Characters outside this set in a field name violate the grammar.

docs/content/docs/headers/obs-fold.md

@@ -18,13 +18,14 @@ A request with an obsolete line-folded header value — a continuation line that
 
 ```http
 GET / HTTP/1.1\r\n
-Host: localhost\r\n
-X-Test: value1\r\n
- continuation\r\n
+Host: localhost:8080\r\n
+X-Test: value\r\n
+ continued\r\n
 \r\n
 ```
 
-The ` continuation` line (starting with a space) is "obs-fold" — it was valid in older HTTP but is deprecated.
+The `X-Test` header value is split across two lines. The second line starts with a space (obs-fold / line folding).
+
 
 ## What the RFC says
 

docs/content/docs/headers/sp-before-colon.md

@@ -16,6 +16,16 @@ weight: 1
 
 A request with a space between the header field name and the colon: `Host : localhost`.
 
+```http
+GET / HTTP/1.1\r\n
+Host: localhost:8080\r\n
+X-Test : value\r\n
+\r\n
+```
+
+Note the space between `X-Test` and the colon.
+
+
 ## What the RFC says
 
 > "No whitespace is allowed between the field name and colon. In the past, differences in the handling of such whitespace have led to security vulnerabilities in request routing and response handling. A server **MUST** reject, with a response status code of 400 (Bad Request), any received request message that contains whitespace between a header field name and colon."

docs/content/docs/headers/whitespace-before-headers.md

@@ -16,6 +16,16 @@ weight: 6
 
 A request with whitespace (SP) before the first header line, between the request-line and the headers.
 
+```http
+GET / HTTP/1.1\r\n
+ \r\n
+Host: localhost:8080\r\n
+\r\n
+```
+
+A line with a single space appears between the request-line and the first header.
+
+
 ## What the RFC says
 
 > "A recipient that receives whitespace between the start-line and the first header field MUST either reject the message as invalid or consume each whitespace-preceded line without further processing of it." — RFC 9112 Section 2.2

docs/content/docs/host-header/duplicate-host-same.md

@@ -16,6 +16,16 @@ weight: 3
 
 A request with two identical Host headers.
 
+```http
+GET / HTTP/1.1\r\n
+Host: localhost:8080\r\n
+Host: localhost:8080\r\n
+\r\n
+```
+
+Two `Host` headers with identical values.
+
+
 ## What the RFC says
 
 > "A server MUST respond with a 400 (Bad Request) status code to any HTTP/1.1 request message that... contains more than one Host header field line..." — RFC 9112 Section 3.2