Skip to content
Tutorials Center
My learning

Topics

Lesson 8 of 38 ยท Setup and Proxy

Intercepting Requests and Responses

Learn how Burp's intercept switch works, how to forward, drop and edit requests and responses, and how intercept rules keep your session usable.

The Intercept feature is what most people picture when they hear "Burp Suite". When it is on, each request pauses inside the proxy before reaching the server. You can read it, change it, and then send it on, or throw it away. Responses can be paused the same way before they reach the browser.

Intercept is powerful but easy to overuse. Modern pages send dozens of requests for scripts, images and analytics, and stopping every one is exhausting. This lesson shows the controls, and then the better habit: leave intercept off most of the time and use it for the single request you want to change.

The intercept panel

Under Proxy > Intercept you see a button, Intercept is on / off, and a message area. When intercept is on and a request arrives, the panel shows:

TEXT
Forward | Drop | Intercept is on | Action | Open browser

Request to https://shop.lab.test:443 [203.0.113.10]
Pretty  Raw  Hex

POST /cart/add HTTP/2
Host: shop.lab.test
Cookie: session=abc123
Content-Type: application/x-www-form-urlencoded

item=book&qty=1

A text mock-up of the real panel. The IP address is a documentation address.

The four actions you use most:

Button What it does
Forward Sends the (possibly edited) message on to its destination.
Drop Discards the message; the browser sees a failed request.
Intercept is on/off Toggles whether new messages are held.
Action Menu: send to Repeater, Intruder, Comparer, and so on.

Editing in the intercept panel

You can edit the message directly in Raw view, or use Pretty for formatting, Hex for byte-level edits, and the Inspector panel on the right for structured fields (query parameters, body parameters, cookies, headers). After you change something, Burp updates Content-Length for you when you forward.

A typical practice flow in your own lab:

  1. Turn intercept on.
  2. In the browser, click "Add to cart".
  3. The request appears; change qty=1 to qty=-1.
  4. Click Forward and look at the page and the response.
  5. Turn intercept off.

The question you are answering: does the server validate quantity, or does it blindly trust the browser?

Intercepting responses

Requests are the usual target, but you can hold responses too: right-click a request and choose Do intercept > Response to this request, or configure the rule below. Editing a response lets you test client-side behaviour: change "isAdmin": false to true and see which hidden menus appear. Remember that this only changes what your browser believes. It proves a flaw only if the server also acts on trust in the client.

Intercept rules

Settings > Tools > Proxy > Request interception rules controls what gets held when intercept is on. Defaults skip some static file types and you can add rules such as:

  • Intercept only when the URL is in scope (see Target scope).
  • Do not intercept requests whose file extension matches js|css|png|jpg|gif|ico.
  • Intercept only POST requests.
  • Intercept requests with a particular parameter or header.

An in-scope-only rule is one of the best habits you can adopt: it stops you from stopping, or accidentally touching, third-party analytics and ad servers.

Keeping the browser usable

  • Turn intercept off before navigating to large pages, then on again for the step that matters.
  • Use HTTP history to look at traffic after the fact. You rarely need to intercept just to read something.
  • Use Repeater for repeated experiments instead of re-clicking in the browser and re-intercepting each time.
  • Right-click an interesting request in history and send it to Repeater; this keeps your browser session clean.

Out-of-band and other traffic

Intercept covers HTTP, HTTPS and WebSocket messages that go through the proxy. WebSocket frames appear in Proxy > WebSockets history and can be held and edited too. Traffic that bypasses the proxy (a native app ignoring system settings, raw TCP, DNS) is invisible to Burp until you route it through.

Try it: a stand-in intercept queue

This stand-in models the mechanics: messages arrive and are held in a queue; the "tester" forwards, edits or drops them. There is no network; only the ideas.

Python Stand-in: an intercept queue

Press Run (or Ctrl + Enter) to see the result here.

Program input ยท what you'd type while the program runs

Type the answers before you press Run, one per line. Each time the program reads a line (with input()), it gets the next line from this box.

Try it: an interception rule

A second stand-in applies rules like "in scope only" and "skip static files" to decide which requests would be held.

Python Stand-in: intercept rules

Press Run (or Ctrl + Enter) to see the result here.

Program input ยท what you'd type while the program runs

Type the answers before you press Run, one per line. Each time the program reads a line (with input()), it gets the next line from this box.

Common mistakes

  • Leaving intercept on and thinking the site is broken.
  • Editing the wrong request because several are queued; check the URL shown at the top.
  • Forgetting that a dropped request may break a flow: a dropped CSRF-protected request cannot be replayed with the old token.
  • Trusting a response edit as proof of a flaw. It only proves the client trusts the data.

Check your understanding

Quick check ยท 4 questions

of 4 answered You scored / 4 ยท perfect!

  1. 1. What does the Drop button do?

    Drop throws the held message away. The browser sees a failure instead of a normal reply.
  2. 2. Why is intercepting only in-scope requests a good rule?

    Scope-limited interception keeps you focused on authorised targets and avoids pointless pauses.
  3. 3. You change a response to say isAdmin is true and an admin menu appears. What does this prove by itself?

    Editing a response changes only your browser's view. A real flaw exists if the server also accepts admin actions from a non-admin.
  4. 4. Which is usually better than leaving intercept on all the time?

    History and Repeater let you study and replay traffic without pausing every page load.

Summary

  • With intercept on, requests (and optionally responses) pause so you can forward, edit or drop them.
  • Edit in Raw, Hex or the Inspector; Burp fixes Content-Length for you.
  • Interception rules (in-scope only, skip static files) keep sessions workable.
  • Prefer history plus Repeater for repeated work; use intercept for the single message you must change live.
  • A response edit shows client trust, not a server flaw.

Next: HTTP history, filters and annotations