How the Web Works for Testers · Core skills
L8. Use an Intercepting Proxy
Capture, inspect, modify and replay HTTP requests with an intercepting proxy, while keeping traffic inside your lab scope.
Lesson 8 of 21 · About 30 minutes including the lab
By the end of this lesson you can
- Explain how an intercepting proxy sits between browser and server.
- Configure Burp Suite Community Edition or ZAP with a target scope.
- Use proxy history and Repeater to modify and resend a request.
- Explain why the proxy CA certificate should only be trusted in a test browser.
Video transcript
The page looks fine. What is the browser really sending? An intercepting proxy sits between your browser and the app, so you can pause, read and change each request. Burp Suite and ZAP are common choices. Point the browser at the proxy, which listens on port 8080 by default. The proxy holds the booking request, so you can read every header and parameter. Change one value, forward it, and watch how the lab app responds. Hidden fields and headers are easy to miss. You see exactly what the server receives, and you can replay it. Use a separate browser profile for testing. Set the proxy scope to your lab target. Write down every value you change. Read before you change anything. Try it in the knowledge check.
Course outlineLesson 8 of 21
Lesson notes
An intercepting proxy is the web tester’s main tool. Your browser sends traffic to the proxy, the proxy shows you each request and response, and you can pause, edit and resend them. This is how you test what the server does when the browser does not behave as the developers expected.
The two common free options are Burp Suite Community Edition from PortSwigger and ZAP (Zed Attack Proxy). Both listen on 127.0.0.1:8080 by default and include an embedded browser that is already configured, which is the easiest way to start.
Set a target scope first. In Burp, add your lab URL (for example http://localhost:3000) under Target, Scope, and filter the HTTP history to in-scope items only. This keeps unrelated sites out of your notes and stops you accidentally sending test traffic elsewhere.
To inspect HTTPS, the proxy creates its own certificate authority and generates certificates on the fly. Your browser must trust that CA, which is why the embedded browser is convenient. Never install a proxy CA in your everyday browser or operating system trust store: anyone who obtained that CA’s private key could intercept your traffic.
The workflow you will use for the rest of the course: browse the app normally with the proxy on, review the HTTP history, send an interesting request to Repeater, change one thing at a time (a parameter, a cookie, a method), resend it and compare the response with the original.
Commands and expected output
Send a request through a running proxy with curl
curl -x http://127.0.0.1:8080 -i 'http://localhost:3000/rest/products/search?q=apple'-x sets the proxy. With Burp or ZAP running and Juice Shop on localhost, the request appears in the proxy history. The response is JSON listing matching products; the exact fields depend on your Juice Shop version.
Hands-on labs
Practice only on these legal targets: your own local lab or machines a platform assigns to you. Never use these techniques on systems you do not have written permission to test.
PortSwigger Web Security Academy
Getting started with Burp SuiteFollow PortSwigger’s getting-started guide to intercept a request, then use Repeater to resend it with a changed parameter.
OWASP Juice Shop
Log in through the proxyRegister a test user, log in with the proxy on, and find the login request in HTTP history. Note the method, path, request body format and what the response returns to the browser.
Practice task
In Juice Shop, use Repeater to resend the product search request three times with different q values. Record how the response changes, and write one sentence on what you would test next.
Key takeaways
- A proxy lets you see and change exactly what the browser sends.
- Set the target scope before browsing so history and tests stay in scope.
- Trust the proxy CA only in a dedicated test browser.
- Change one thing at a time in Repeater and compare responses.
Framework mapping
Sources and further reading
1. What is the main purpose of an intercepting proxy in web testing?
2. Why set a target scope in Burp or ZAP before browsing?
3. Where should you trust the proxy’s CA certificate?
4. Which Burp tool lets you edit and resend a single request manually?