WEB / LEARNING PATH
Web learning path
Move from request initiation to browser state and server decisions; begin with the learning stop you need.
Choose your Web learning path.
Move from request initiation to browser state and server decisions; begin with the learning stop you need.
- Build the big picture
Open WEB-01.01 and WEB-01.02 from The big picture. Identify browser, application and resource roles, then follow the steps between a request and its visible outcome.
- Move to the stop matching your question
Choose one of the seven learning groups or select from the map’s 22 modules. Follow lesson prerequisites; compare the Core mechanism, Red assumptions that may fail, and Blue secure development and defense.
- Produce a learning result
Select an artifact field, write a reason in lesson practice, or compare a prediction with observation in a linked manual lab. Note what changed and which evidence remains missing.
You can explain who makes a request or state decision, using which data and condition, and separate observed outcomes from outcomes that are only possible.
Before you begin
- Opening a browser tab, copying an address and editing a text field are enough to start.
- Start with WEB-01.01 to identify the roles, then follow the first request in WEB-01.02. You can move to Red/Blue after the Core narrative and first practice.
- Manual Node labs need Node.js 20+ and a terminal; lessons and the browser workbook do not depend on that setup.
Who is this series for?
For beginners learning Web mechanisms, security students investigating request and state decisions, and developers verifying secure development and defense controls through concrete evidence.
Seven groups, 22 modules
The big picture
Connect browser, application and resource roles to a request and its visible outcome.
Connections and trust
Explain the distinct outcomes of name resolution, transport and TLS decisions.
Addresses and HTTP
Compare URL, HTTP message, representation and cache fields within one request.
Browser and state
Identify the different owners of source, DOM, policy and storage state.
Identity and access
Separate session or credential acceptance from resource permission decisions.
Servers and APIs
Follow which data is changed by the server pipeline, API contract and persistence decision.
Data and operations
Use cache, queue, runtime and audit records to identify outcomes, coverage and recovery boundaries.
How will you demonstrate learning?
- Explain an HTTP outcome through status, body and the subsequent browser step.
- Demonstrate URL/origin, cookie/session and authentication/permission distinctions using concrete fields.
- Identify how a changed condition alters a branch decision and which work is skipped.
- State an observation’s producer, coverage and missing evidence, then describe how to check a safe correction.
Study scope
Scenes are synthetic teaching models, not live records of your browser or a remote system.
Manual lab results apply to the supplied local fixture and workbook question, not every other environment.
A local assessment result is not a public certificate; records last for the assessment service session. Lesson practices remain available offline.