Configuring Burp Proxy and Browser Setup
What you'll learn: How to route browser traffic through Burp Suite and establish trusted interception for secure web application testing.
The Core Concept
Burp Suite acts as a man-in-the-middle between your browser and target applications, but it won't work until you configure your browser to route traffic through it. Think of Burp as a traffic inspector at a checkpoint—your browser needs to know to send all vehicles (HTTP/HTTPS requests) through that checkpoint instead of directly to their destination.
Browser Proxy Configuration
By default, Burp Proxy listens on 127.0.0.1:8080. You must configure your browser's proxy settings to forward all HTTP and HTTPS traffic to this address. Many testers use FoxyProxy (a browser extension) to quickly toggle between direct connections and proxied traffic, avoiding the need to repeatedly change system settings.
Installing CA Certificates
When Burp intercepts HTTPS traffic, it generates its own SSL certificates on-the-fly. Without trusting Burp's Certificate Authority (CA), your browser will throw security warnings for every HTTPS site. To fix this:
- Navigate to
http://burpwhile proxied through Burp - Download the CA certificate
- Import it into your browser's trusted root certificates
This tells your browser: "I trust Burp to decrypt and inspect my HTTPS traffic."
Upstream Proxy Configuration
Sometimes you need to test through additional network layers—corporate proxies, anonymization tools like Tor, or cloud-based testing platforms. Burp's upstream proxy settings let you chain proxies together: Browser → Burp → Upstream Proxy → Target. This is configured in Burp's User Options → Connections → Upstream Proxy Servers.
Key Takeaway: Proper Burp configuration requires three steps: setting your browser to proxy through Burp's listener, installing Burp's CA certificate to avoid HTTPS warnings, and optionally configuring upstream proxies for complex network scenarios.