Headers

Problem

What becomes confusing, fragile, or impossible without understanding headers? This lesson answers that through explanation, a worked example, two runnable exercises, and a reference solution. No teacher-supplied worksheet is required.

HTTP and hypertext scale by exchanging representations through standardized methods, status codes, headers, links, and forms.

Concept explanation

Headers belongs to “HTTP is the application protocol”. headers must be connected to layer below by tracing representation, ownership, control, and failure. HTTP semantics live in method, target, status, headers, and representation—not in client-side conventions.

For headers, trace concrete input, state transition, output, and failure through a request/response contract whose method, status, headers, representation, and next actions are observable.

A client sends a request; a server returns a representation plus metadata. Hypermedia controls advertise valid next actions. Apply that model to supplied normal, boundary, and failure cases; each case below names its input and expected evidence.

Example bank

Compare normal, boundary, failure, and cross-layer cases. Predict each observation before revealing the explanation.

Worked example

Start from supplied lab.sh. Focus: Trace headers end-to-end while running: Fetch one document and annotate request line, status line, every header, and body boundary.

1. Run: chmod +x lab.sh && ./lab.sh
2. Save baseline evidence. Compare curl -v output, request method, status, cache metadata, redirects, and representation bytes.
3. Boundary case: At every headers boundary, label owner and representation during: Send HEAD and compare it with GET.
4. Failure case: Locate first layer where evidence diverges during: Request a missing path and keep non-2xx response body and status.

RESULT
Trace explains GET returns representation, HEAD omits body, missing path has observable status without transport failure. without skipping any conversion, queue, process, protocol, or storage boundary. Starter-level baseline: headers.txt begins with an HTTP status line; body.txt contains the representation; byte count is greater than zero.

Starter material

Create lab.sh, paste this exact content, then run the command below.

#!/usr/bin/env sh
set -eu
url="${1:-https://example.com/}"
printf '%s\n' '# headers'
curl -sS -D headers.txt -o body.txt "$url"
sed -n '1,12p' headers.txt
printf 'body bytes: ' && wc -c < body.txt

STOP / CLEANUPNo background process. Remove headers.txt and body.txt only after saving evidence.

Independent exercise

Remove one abstraction: headers

1. Create second case from blank file: At every headers boundary, label owner and representation during: Send HEAD and compare it with GET.
2. Then create controlled failure: Locate first layer where evidence diverges during: Request a missing path and keep non-2xx response body and status.
3. Use curl · Chromium Network · server logs to prove behavior, then repair controlled failure.
4. Compare result against supplied acceptance checks and reference approach before marking complete.

Expected result

• Trace explains GET returns representation, HEAD omits body, missing path has observable status without transport failure. without skipping any conversion, queue, process, protocol, or storage boundary.
• headers.txt begins with an HTTP status line; body.txt contains the representation; byte count is greater than zero.
• Controlled headers failure produces captured evidence; repair restores stated invariant without hiding error.

Hints

Solution

Attempt both exercises before opening reference approach.