Endpoint BayISSUE #3 of 45

http basics · request · response

RestaVSThe 401 Bandit

Resta saysMost web APIs run on HTTP: a client sends a request, the server returns a response.

HTTP is the request/response protocol of the web. A request has a method, URL, headers, and optional body; a response has a status code, headers, and a body. It's stateless — each request stands alone, carrying whatever context (tokens, etc.) it needs. Understanding this round-trip is the foundation of every web API.

Power-ups you unlock

Request → server → response
Request: method, URL, headers, body
Response: status, headers, body
HTTP is stateless — each request stands alone

The 401 Bandit attacks — common mistakes

Assuming the server remembers prior requests
Forgetting to send needed headers/auth each time
Confusing the URL with the full request

Boss battleLabel the four parts of an HTTP request for a login call.

Example code

<!doctype html><html><head><meta charset="utf-8"></head>
<body style="background:#06040d;color:#e6e0ff;font-family:monospace;padding:20px"><pre>POST /login            ← method + URL
Content-Type: application/json   ← header
{ "email": "...", "pw": "..." }  ← body
→ 200 OK { "token": "..." }      ← response</pre></body></html>

▶ Open the interactive comic issue

‹ Why Apis · Machines Talking To Machines Http Methods · GET · POST · PUT · PATCH · DELETE ›