Inspect an HTTP Conversation

Observe request and response metadata for a site you own or a documentation endpoint.

3h practical labAndroid · Termux
OBJECTIVE

Observe request and response metadata for a site you own or a documentation endpoint.

TIME PLAN

Prepare 20m · Build 110m · Verify 30m · Document 20m

Working boundary

Work only inside the folder created by Smartphone-Academy.py prepare http-observation. Use the supplied samples or systems you personally administer.

Prepare the Termux workspace

Open Termux in the Academy root and prepare this lab with the local companion. It creates safe samples, notes and evidence files under your Termux account.

Android + Termuxpython Smartphone-Academy.py prepare http-observationNo root. Use the supplied files and keep the workspace under $HOME.

Practical mission

  1. Send a HEAD request before downloading content
  2. Follow and document a redirect chain
  3. Compare selected security and caching headers
  4. Save a redacted transcript that excludes cookies and tokens
EVIDENCE TO PRODUCE

An annotated transaction showing method, status, headers, redirects and timing.

Quality gate

The deliverable states a clear scope and date for Inspect an HTTP Conversation.
A second learner can reproduce the commands and paths.
Original samples remain unchanged and verifiable.
Limitations are recorded beside the conclusions.

Analyst reflection

Which result from “Save a redacted transcript that excludes cookies and tokens” would need more evidence before it could support an operational decision?

Complete in Termux

After checking the evidence, run python Smartphone-Academy.py complete http-observation. Progress is stored locally in the Termux home directory.

11 · Network Observation

Continue learning

Back to Smartphone Academy

Previous lesson

Audit Listening Ports Locally

Next lesson

Reason from Packet Metadata