Glossary sidebar collapsed by default

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

Author: MDA2AV

docs/content/docs/_index.md

@@ -2,7 +2,7 @@
 title: Glossary
 description: "Glossary — Http11Probe documentation"
 sidebar:
-  open: true
+  open: false
 ---
 
 Reference documentation for every test in Http11Probe, organized by topic. Each page explains the RFC requirement, what the test sends, what response is expected, and why it matters.

docs/content/docs/content-length/_index.md

@@ -3,7 +3,7 @@ title: Content-Length
 description: "Content-Length — Http11Probe documentation"
 weight: 6
 sidebar:
-  open: true
+  open: false
 ---
 
 The `Content-Length` header indicates the size of the message body in bytes. Its grammar is strict: `Content-Length = 1*DIGIT`. Any deviation — non-numeric characters, plus signs, leading zeros, negative values, overflow — can cause parsers to disagree on body boundaries.

docs/content/docs/headers/_index.md

@@ -3,7 +3,7 @@ title: Header Syntax
 description: "Header Syntax — Http11Probe documentation"
 weight: 4
 sidebar:
-  open: true
+  open: false
 ---
 
 HTTP header fields follow a strict grammar: `field-name ":" OWS field-value OWS`. RFC 9112 Section 5 and RFC 9110 Section 5.6.2 define what constitutes a valid header. Violations can lead to parser disagreements and smuggling.

docs/content/docs/host-header/_index.md

@@ -3,7 +3,7 @@ title: Host Header
 description: "Host Header — Http11Probe documentation"
 weight: 5
 sidebar:
-  open: true
+  open: false
 ---
 
 The Host header is the only header where RFC 9112 **explicitly mandates a 400 response** for violations. This makes the Host header tests the strictest in the entire suite — close or timeout is NOT acceptable.

docs/content/docs/line-endings/_index.md

@@ -3,7 +3,7 @@ title: Line Endings
 description: "Line Endings — Http11Probe documentation"
 weight: 2
 sidebar:
-  open: true
+  open: false
 ---
 
 RFC 9112 Section 2.2 defines that HTTP/1.1 messages use **CRLF** (`\r\n`) as the line terminator for the request-line and header fields. Deviations from this — bare LF, bare CR — are framing violations that can lead to request smuggling or parser confusion.

docs/content/docs/malformed-input/_index.md

@@ -3,7 +3,7 @@ title: Malformed Input
 description: "Malformed Input — Http11Probe documentation"
 weight: 8
 sidebar:
-  open: true
+  open: false
 ---
 
 These tests send pathological, oversized, or completely invalid payloads. The goal is not RFC compliance (there's no RFC section for "what to do with binary garbage") — it's robustness. A well-implemented server should reject gracefully, not crash, hang, or consume unbounded resources.

docs/content/docs/request-line/_index.md

@@ -3,7 +3,7 @@ title: Request Line
 description: "Request Line — Http11Probe documentation"
 weight: 3
 sidebar:
-  open: true
+  open: false
 ---
 
 The request-line is the first line of an HTTP request: `method SP request-target SP HTTP-version CRLF`. RFC 9112 Section 3 defines its grammar strictly. Malformed request-lines are a common vector for parser confusion.

docs/content/docs/smuggling/_index.md

@@ -3,7 +3,7 @@ title: Request Smuggling
 description: "Request Smuggling — Http11Probe documentation"
 weight: 7
 sidebar:
-  open: true
+  open: false
 ---
 
 HTTP request smuggling exploits disagreements between HTTP processors about where one request ends and the next begins. When two servers parse the same byte stream differently, an attacker can hide a request inside another.