Web Basics for Bug Bounty Hunters
Web basics for bug bounty means understanding how a browser and server exchange data. It includes HTTP requests and responses, methods, headers and status codes, cookies and sessions, the same-origin policy, and how HTML, JavaScript and APIs fit together. Every vulnerability class later builds on these mechanics, so weak basics make bugs hard to see.
Stage: Getting Started · Part of the Bug Bounty Hunter roadmap · Last reviewed 19 November 2026
What to learn in Web Basics
- Read a raw HTTP request and identify method, path, headers and body
- Explain how cookies, sessions and tokens keep a user logged in
- Describe the same-origin policy and what CORS relaxes
- Inspect network calls in browser developer tools
- Tell apart client-side and server-side processing of input
Web Basics interview questions
What does the same-origin policy do?
It stops a script loaded from one origin, defined by scheme, host and port, from reading responses of another origin. This protects a user's logged-in sessions from malicious pages. CORS is a controlled way for a server to loosen the restriction.
What is the difference between a session cookie and a JWT?
A session cookie holds an identifier the server looks up in its own store. A JSON Web Token carries signed claims itself, so the server can verify it without a lookup. Each has different risks, such as theft, weak signing or poor revocation.
Where Web Basics fits in the Bug Bounty Hunter roadmap
Web Basics belongs to the Getting Started stage (beginner level), which takes about 25 hours. How bounties work.
Other units in this stage
Back to the full Bug Bounty Hunter roadmap