Skip to content
Tutorials Center
My learning

Topics

Lesson 9 of 38 ยท Setup and Proxy

HTTP History, Filters and Annotations

Read Burp's HTTP history like a log. Filter by scope, type and status, search bodies, add comments and highlights, and send items to other tools.

Everything that flows through the proxy is recorded in Proxy > HTTP history, a table with one row per request. A busy page can add hundreds of rows in a few seconds, so reading history well is mostly about filtering: hiding the noise so the interesting requests stand out.

Think of the history as a flight recorder. You rarely need to watch it live; you browse the application normally, then analyse what happened afterwards, using intercept only for the one request you want to change.

What each column tells you

A typical history table (text mock-up) looks like this:

TEXT
#    Host                  Method  URL                    Params  Status  Length  MIME    Title
41   shop.lab.test         GET     /                      -       200     5,312   HTML    Lab Shop
42   shop.lab.test         GET     /static/app.js         -       200     48,201  script
43   shop.lab.test         POST    /login                 yes     302     0       -
44   shop.lab.test         GET     /account               -       200     3,904   HTML    My account
45   cdn.analytics.test    GET     /collect?e=view        yes     204     0       -
  • #: sequence number, handy to reference ("see request 43").
  • Params: whether the request carried parameters.
  • Status and Length let you spot differences quickly; a different length for the same URL often means different content.
  • MIME and Title give a quick sense of what came back.

Click a row to see the full request and response below, in Pretty, Raw, Hex and Render views.

Filtering

Click the filter bar above the table. The filter dialog offers several groups:

Filter Use it to
Filter by request type Show only in-scope items, only requests with parameters, hide items without responses
Filter by MIME type Hide images, CSS and fonts; keep HTML, JSON and scripts
Filter by status code Show only 2xx, or only 4xx and 5xx to hunt for errors
Filter by search term Show rows containing a word or regular expression in request or response
Filter by file extension Hide .js, .css, .gif
Filter by annotation Show only rows you commented or highlighted
Filter by listener Show traffic from one of several listeners

The most useful single choice: Show only in-scope items. Combine it with "hide static content" and a history of 800 rows can shrink to 40.

Filters only hide rows from view; nothing is deleted, and you can change filters at any time.

Searching

You can search the whole history (or a Repeater response) for text. Useful searches while analysing an app:

  • password, token, secret, apikey: look for credentials or tokens in responses and scripts.
  • Set-Cookie: find where sessions are issued.
  • error, exception, stack, trace: find verbose error pages.
  • Server names and versions such as X-Powered-By.

Enable regex for patterns, and negative search to exclude matches. Regular expressions are worth learning, because they turn a vague "find anything like a token" into one precise query.

Annotations: comments and highlights

Right-click a row to add a comment (a note) or a highlight (a colour). Use them as a lightweight to-do system:

  • Red: confirmed issue.
  • Orange: suspicious, to test.
  • Green: checked, nothing found.
  • Comment: "uses id param, try other user's id".

Later, filter by annotation to see only what you marked. Good notes during a test save an hour when you write the report.

Sending items to other tools

Right-click any row to choose Send to Repeater, Send to Intruder, Send to Comparer, Send to Organizer, or Add to scope. You can also copy as a curl command (handy for documentation), or save the item. The context menu is the glue of the suite: you rarely type a request from scratch.

  • WebSockets history: messages on WebSocket connections, with direction and content.
  • Logger: records requests from every tool (Repeater, Intruder, extensions), not just the proxy.
  • Target > Site map: the same data arranged as a tree by host and path; see Site map.

Try it: filter a history log

This stand-in models history as a list of records and applies the most useful filters: in-scope, hide static files, status class and text search.

Python Stand-in: filtering an HTTP history

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: annotate and rank

A second stand-in tags rows with a colour and a note, then lists what to test first. It mirrors using highlights as a to-do list.

Python Stand-in: annotations as a to-do list

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.

Habits that pay off

  • Browse first, filter second. Click through every feature once with intercept off.
  • Keep scope set, so "show in-scope only" is always meaningful.
  • Write comments as you go, not at the end.
  • Do not search for secrets and paste them into chats. Redact first, as the ethics lesson advises.
  • Clear very old history if Burp slows down, after saving anything you need.

Check your understanding

Quick check ยท 4 questions

of 4 answered You scored / 4 ยท perfect!

  1. 1. What does filtering the HTTP history do?

    Filters only change what is displayed. You can change or clear them at any time.
  2. 2. Which filter combination best reduces noise during an authorised test?

    Scope plus hiding static files leaves the dynamic requests to the target, which is where testing happens.
  3. 3. Why add comments and highlights to history items?

    Annotations let you filter and revisit the suspicious or confirmed items later.
  4. 4. Which tool records requests from Repeater and Intruder as well as the Proxy?

    Proxy history only holds proxied traffic; Logger records requests from all tools and extensions.

Summary

  • HTTP history is a log of everything the proxy saw; reading it well is mostly filtering.
  • Useful filters: in-scope, MIME type, status class, extension, search term and annotations.
  • Search with plain text or regular expressions to find tokens, errors and technology hints.
  • Comments and highlights turn history into a work list.
  • Right-click to send items to Repeater, Intruder, Comparer and Organizer.

Next: Proxy match and replace