Paths/Backend Engineer/HTTP & Networking / Request Lifecycle
Map Outcomes to Status Codes
The status code is part of the contract - it tells the client whether to retry, to fix its request, or to give up. Write the mapping.
Validator
⏱ 0:00
IDLE — checks run live as you type commands; submit when done
01Requirements
live checks- File ~/http/status-codes.md exists○
- The document maps the outcomes to status codes○
- The document states which codes are safe to retry○
02Walkthrough
1 of 4 revealed- 01
Create the http directory
The status code table is a reference the whole team reads.
mkdir -p ~/http - 3 locked · each failed submit reveals one
03Stuck?
0 of 3 revealedTake a hint without losing the lab — each one points at the thing to look at, not at the answer.
04AI Tutor
guides, never solvesTell me what you're stuck on — I'll nudge, not solve. Which requirement are you looking at?
04Notebook
saved locally in this browserlearner@lab — ubuntu:24.04
Session is disposable
↑/↓ recalls commands · Ctrl+Enter submits · type help for the command list