Catch a token in a redirect
Practitioner 20 ptsGoal: Read the one-time token the server put in a 302 Location header.
Capture it yourself — real traffic
- Open Wireshark on your active interface and start a capture. Display filter for this level:
http.response.code == 302. No GUI?sudo tcpdump -i any -w cap.pcap port 9080. - Open the plaintext lab and click Generate traffic once.
- Stop the capture. The secret is in the
Locationheader on the/old-report302 response. Expand the 302's headers and readLocation: /reports/view?token=…— take thetoken.
Open the plaintext lab (:9080) →
Genuinely unencrypted — the secret exists only on the wire, never on the page.
Hints
Open in order — they nudge, not solve.
Hint 1
The page hit /old-report, which 302-redirects. Find the response (filter http.response or http.response.code == 302).
Hint 2
Expand its headers for Location: — the browser followed it instantly, but the header is right here.
Hint 3
The token in that Location URL (REDIR-…) is the answer.