πŸ‡¬πŸ‡§ πŸ‡¨πŸ‡Ώ
Chapter 5

The Queen's Cipher

═══════════════════════════════════════════════════════════════════ CHAPTER 5: THE QUEEN'S CIPHER ═══════════════════════════════════════════════════════════════════ You know the truth. Duchess Athena Authenticate is the spy. But knowing isn't enough. You must PROVE it. Set a trap. Navigate the throne room's security. Present your evidence before the Queen. All your skills will be tested. One final sequence of requests stands between justice and the spy's escape. The kingdom's fate rests in your cURL commands. ═══════════════════════════════════════════════════════════════════
Skills You'll Learn: All skills combined in final confrontation

Paste your token to sync progress:

5-1 The Bait
Not Done
Create fake intelligence about a 'Malwarian contact.' If Athena is the spy, she'll try to intercept it.
Command
curl -X POST https://httpqueen.net/intelligence/report \ -H "Authorization: Bearer YOUR-TOKEN" \ -H "Content-Type: application/json" \ -b cookies.txt -c cookies.txt \ -d '{"classification": "top_secret", "subject": "malwarian_contact", "content": "Meeting at midnight", "tracking_id": "TRAP-001"}'
Security testing often uses canary tokens - unique markers that trigger when accessed. The spy will reveal herself.
Old Margot whispers: "POST fake intelligence. Include a tracking marker in your cookies."
5-2 Throne Room Maze
Not Done
Navigate to the throne room. Security has implemented multiple redirects and checkpoints.
Command
curl -L https://httpqueen.net/castle/throne-room \ -H "Authorization: Bearer YOUR-TOKEN" \ -H "X-Security-Clearance: royal-investigator" \ -b cookies.txt -c cookies.txt
Complex navigation: Redirects can strip headers! Some need to be re-sent. Cookies help maintain state across redirects.
Old Margot whispers: "Follow redirects with -L, maintain auth headers through each hop, keep cookies active."
5-3 Present Evidence
Not Done
Before accusing the Duchess, you must formally clear the other suspects. Present evidence to eliminate each one.
Command
curl -X POST https://httpqueen.net/investigation/eliminate \ -H "Authorization: Bearer YOUR-TOKEN" \ -H "Content-Type: application/json" \ -d '{"suspect": "cache", "evidence": "budget_items_for_sick_mother", "verdict": "not_spy"}'
Process of elimination in APIs: Sometimes you must explicitly handle all cases. Each POST updates the investigation state.
Old Margot whispers: "POST elimination requests for each suspect with evidence why they're NOT the spy."
5-4 The Accusation
Not Done
Present your complete case against Duchess Athena Authenticate to Queen Elara.
Command
curl -X POST https://httpqueen.net/throne/accuse \ -H "Authorization: Bearer YOUR-TOKEN" \ -H "Content-Type: application/json" \ -d '{"accused": "duchess_athena", "evidence": {"routing": "all_traffic_via_athena", "ink": "security_seal_on_murder_note", "session_control": "only_she_can_revoke", "interception": "knew_investigation_details"}}'
Critical API calls should be idempotent where possible. This accusation changes everything - make sure the payload is complete.
Old Margot whispers: "Compile ALL evidence: the routing header, the ink analysis, the session control, the interceptions. One comprehensive POST."
5-5 Spring the Trap
Not Done
The Duchess denies everything. Time to reveal your trap - show that she accessed the fake intelligence you planted.
Command
curl https://httpqueen.net/intelligence/trap-status/TRAP-001 \ -H "Authorization: Bearer YOUR-TOKEN"
The final skill: bringing everything together. Real API work combines all these concepts in complex workflows.
Old Margot whispers: "GET the trap status. The tracking marker will show if and when it was accessed, and by whom."