Intercepting and Modifying HTTP Traffic
What you'll learn: How to use Burp Proxy to capture and alter web requests and responses in real-time during security testing.
The Core Concept
Now that you've configured Burp Proxy and your browser, you can intercept HTTP traffic flowing between your browser and web applications. Think of Burp as a security checkpoint guard who can stop every vehicle (HTTP request/response), inspect its contents, and even rewrite documents before waving it through.
When intercept is enabled, Burp pauses each request before it reaches the server. You see the raw HTTP message—method, headers, parameters, and body—and can modify any part of it. This lets you test how applications respond to unexpected or malicious input that you couldn't easily send through a normal browser.
Why This Matters
Browsers enforce certain restrictions and automatically format requests. Burp lets you bypass these limitations. You can:
- Change parameter values to test for injection flaws or logic bugs
- Modify headers like
User-Agent,Authorization, or custom application headers - Alter the request body in POST requests (JSON, XML, form data)
- Change HTTP methods (GET to POST, POST to DELETE)
- Intercept responses and modify what the server sends back to test client-side validation
Practical Workflow
With Burp Proxy listening and intercept on, browse to a target application. When you submit a form or click a link, the request freezes in Burp's Intercept tab. You'll see the raw HTTP message. Edit any field directly—change a price parameter from 100 to 1, add SQL injection payloads, or alter session tokens. Click "Forward" to send your modified request to the server. Toggle intercept for responses if you want to modify server replies before your browser processes them.
Key Takeaway: Burp Proxy's interception capability transforms you from a passive browser user into an active tester who controls every byte of communication, enabling thorough security assessment of web applications.