routeup inspect

routeup inspect shows the retained request and response data for a request that was recorded by an opted-in route.

routeup inspect <request-id>

Get the request id from routeup logs:

routeup logs example-app --follow
# 12:41:03 public example-app POST /api/webhooks/github 200 38ms req_abc123

routeup inspect req_abc123

Example output

Request req_abc123

Metadata
--------
Source: public
Route: example-app
Target: /:8080
Status: 200
Duration: 38ms
Method: POST
Path: /api/webhooks/github
Host: example-app.try.routeup.dev

Request
-------
Capture: complete
Body bytes: 842
X-Github-Event: push
X-Hub-Signature-256: sha256=abc...

Body
----
{"ref":"refs/heads/main","repository":{"full_name":"..."},...}

Response
--------
Capture: complete
Body bytes: 14
Content-Type: text/plain; charset=utf-8

Body
----
{"ok":true}

Enabling capture

Capture is disabled by default. Enable it per-route in routeup.json:

{
  "name": "example-app",
  "port": 8080,
  "capture": {
    "request": true,
    "response": true,
    "redact_headers": ["authorization", "cookie"]
  }
}

request captures incoming headers and body. response captures the upstream’s headers and body. Both are independent — you can enable either or both.

Headers listed in redact_headers are omitted from the captured copy but are still forwarded to the upstream service unchanged.

Retention

Captured data is stored in the same in-memory ring buffer as request logs (last 1,024 entries). It is cleared when the agent restarts. Each captured request and response message is independently bounded to 256 KiB. Larger bodies are captured as a prefix and marked partial.

Privacy

routeup inspect is only accessible over the local Unix socket (mode 0600). It is not reachable from the network.