Burp Suite 101: Reading and Manipulating GET Requests

2026-08-27

Every button click, page load, and "view profile" link on the web boils down to a plain-text request your browser builds and fires at a server. Most people never see that text -- the browser assembles it, sends it, and renders whatever comes back, all invisibly. Burp Suite's entire value proposition is removing that invisibility: it sits between your browser and the internet, shows you the exact request before it leaves your machine, and lets you change any part of it before it goes. Once you can see and edit that layer, "the app decided what to show you" quietly becomes "you decided what to ask for."

What a GET request actually is

A GET request is one of the HTTP methods browsers use to ask a server for something, and it's the one doing the work every time you load a page, click a link, or follow a bookmark. Stripped down, it looks like this:

GET /account/profile?user_id=4471&view=summary HTTP/1.1
Host: example.com
User-Agent: Mozilla/5.0 (...)
Cookie: session=a93f...c02e
Referer: https://example.com/dashboard
Accept: text/html

Three parts matter most. The path (/account/profile) tells the server which resource you want. The query string (everything after the ?) passes parameters as plain key-value pairs -- user_id=4471 and view=summary here -- and it's fully visible in the URL bar, browser history, and server access logs, which is exactly why it's a bad place for anything sensitive. The headers carry metadata about the request: Cookie for session state, Referer for where you came from, User-Agent for what client you're claiming to be. Unlike POST, a GET request has no body -- everything it sends has to fit in the path, the query string, or the headers, which is part of why so much application state ends up sitting in a URL where anyone looking over your shoulder, or your ISP, or a browser history sync service, can see it.

Getting Burp in the middle

Burp Suite (the Community edition is free and enough for all of this) works as an intercepting proxy: your browser sends traffic to Burp instead of directly to the internet, Burp shows it to you, and only then forwards it on. Setting that up is three steps:

  1. Point your browser at Burp's proxy listener. By default Burp listens on 127.0.0.1:8080. Set that as your browser's HTTP/HTTPS proxy -- directly in browser settings, or with an extension like FoxyProxy if you want to flip it on and off without digging through menus every time.
  2. Install Burp's CA certificate. HTTPS traffic is encrypted between your browser and the server, so to read it Burp has to terminate the TLS connection itself and re-encrypt it with its own certificate -- a deliberate, visible man-in-the-middle that you're installing on your own machine, not doing to someone else. Visit http://burpsuite while proxied through Burp, download the CA cert, and add it to your browser or OS trust store. Skip this and every HTTPS site just throws certificate warnings at you.
  3. Turn on Intercept. In the Proxy tab, "Intercept is on" pauses every request before it leaves your browser, showing you the raw text and giving you a chance to edit it. Turn it off once you're done actively tampering -- left on, it pauses every request on every site you visit, which gets old fast.

Reading live traffic

With Intercept off but the proxy still running, browse normally and watch the Proxy > HTTP History tab fill up with every request your browser made -- every image, script, API call, and page load, each one inspectable after the fact. This alone is worth the setup: it's the fastest way to see what a page is actually doing under the hood, including requests to endpoints that never show up in the page source because JavaScript fired them dynamically. Click any entry and you get the full raw request on one side, the full raw response on the other.

Manipulating the request

This is where Burp stops being a packet sniffer and starts being a testing tool. Right-click any request in the history and send it to Repeater, which lets you edit and resend it as many times as you want, watching the response change with every tweak -- no need to re-trigger the action in the browser each time.

A few of the most common things worth trying against a GET request, assuming you have permission to test the target:

None of this requires writing code. It requires noticing that a request is just text, and that the server has no way of knowing whether that text came from your browser doing what it was told or from you doing something else with the same shape.

Where it breaks