Skip to main content

A private request bin on your machine

Run Buggregator and send requests to http://http-dump@127.0.0.1:8000/<any path>. Each one is caught whole: method, URL, query, headers, cookies, body and uploaded files, plus a cURL command to send it again. It all stays on your machine and works without internet, so tokens and customer data in the payload go nowhere.

Steps

1. Start Buggregator

Bind the port to 127.0.0.1, so only your machine can reach the bin.

bash
docker run --pull always \
  -p 127.0.0.1:8000:8000 \
  ghcr.io/buggregator/server:latest

2. Send a request to any path

http-dump as the URL user name marks the request. Any method and almost any path work. Paths Buggregator uses itself, such as /api/, /mock/ or ones ending in /store, go elsewhere.

bash
curl -X POST 'http://http-dump@127.0.0.1:8000/orders/42?source=test' \
  -H 'Content-Type: application/json' \
  -d '{"status": "paid"}'

Buggregator answers 200 with {"status":true}.

3. Or mark it with a header

When the sender cannot put a user name in the URL but can set a header:

bash
curl 'http://127.0.0.1:8000/orders/42' \
  --header 'X-Buggregator-Event: http-dump'

4. Read the requests

Open http://127.0.0.1:8000. Each request shows its method, full URI, query parameters, form data, headers, cookies and uploaded files, which you can download. The cURL command has a copy button.

5. Keep the bin across restarts

By default the bin lives in memory and is empty after a restart. Give Buggregator a database file to keep it. This setting is for Buggregator itself.

bash
docker run --pull always \
  -p 127.0.0.1:8000:8000 \
  -e DATABASE_DSN=/data/buggregator.db \
  -v buggregator-data:/data \
  ghcr.io/buggregator/server:latest

6. Empty it

This also clears the HTTP proxy captures and the mock server's call history.

bash
curl -X DELETE http://127.0.0.1:8000/api/events \
  -H 'Content-Type: application/json' -d '{"type": "http-dump"}'

Why it works

Buggregator treats any request marked with http-dump, by URL user name, Basic Auth or header, as a dump and stores it in its own SQLite database. There is no account and no public URL, so nothing is sent anywhere. In Docker Compose, other services reach the same bin at http://http-dump@buggregator:8000/....

Checked on with Buggregator v2.13.0

Setup in 60 seconds

No registration. No account. Start it and point your app at it.

1

Start Buggregator

One file, installed with one command. The web UI opens on port 8000. Prefer containers? Use the Docker tab.

$ curl -fsSL https://raw.githubusercontent.com/buggregator/server/master/scripts/install.sh | sh
$ HTTP_ADDR=127.0.0.1:8000 \
  SMTP_ADDR=127.0.0.1:1025 \
  VAR_DUMPER_ADDR=127.0.0.1:9912 \
  MONOLOG_ADDR=127.0.0.1:9913 \
  PROXY_ADDR=127.0.0.1:8080 \
  ~/.local/bin/buggregator

The script picks the file for your CPU: Intel/AMD or ARM.

One file for Linux, macOS and Windows, about 40 MB. Nothing else to install.

This run line keeps it on this computer. Without the *_ADDR settings it listens on all network interfaces

Rather not run a script? Download the file yourself

Runs on Windows, macOS and Linux, on Intel/AMD and ARM.

Prefer not to do it yourself? Your AI agent can set Buggregator up for you