Replay and editing requests

Opening Replay

From any captured request's detail view, tap Replay / Edit. You'll see the same method, URL, headers, query parameters, and body the original request sent — all editable before you send it again.

What you can change

• Method, path, and query parameters
• Any header — add, remove, or edit a value
• The request body, including re-formatting a JSON payload

Send it, and the response comes back inline in the same view — no separate screen to jump to.

Quick Actions

A few common experiments are one tap instead of a manual edit:

• Remove Authentication — strips both the Authorization and Cookie headers in one tap, to test whether a request actually requires them.
• Delay — hold the send for a configurable amount of time, to see how your app handles a slow response.
• Throttle — pace the response at a chosen network profile instead of full speed.

Delay and Throttle work by adding a real, temporary rule scoped to that one request, sending it, then removing the rule — the same mechanism as a standing Rule, not a separate simulation.

Replay ×N — checking consistency

A single replay tells you what happened once. Replay ×N repeats the same request several times in a row and reports whether the outcome, latency, and response body actually stayed consistent across the repeats — useful for the class of bug that "sometimes" happens, where a single manual retry tells you almost nothing.

Making sense of what you changed

When you replay an edited request, Hollowport reads back what actually changed in plain language — "Remove Authentication," "Add Delay," "Modify Cookie" — instead of a raw field-level diff, so the summary matches how you'd describe the change to a teammate. A change that doesn't match one of these recognized patterns still gets a plain field count, never a guess dressed up as a label.

Next: did the change explain it?

Replay two versions of the same request — as originally captured, and with something changed — then open Compare for a summary of what changed and a hedged, evidence-backed read on whether that's actually what caused the difference.