Skip to content
All tools
WebRuns locallyNo account

HTTP request replayer

Craft and replay HTTP requests with arbitrary methods, headers, and bodies, and read the raw response - a Repeater that runs in your browser.

Open in ctfpal

Web challenges are a loop: change one thing about a request, send it, read the response. A browser makes that loop slow because it insists on being a browser - it will not send PUT, it normalises your headers, and it re-runs the whole page every time.

Sending the request directly removes all of that. You see exactly what went out and exactly what came back, headers included, and you change one variable at a time - which is the only way to attribute a change in behaviour to the thing you actually changed.

What to vary

  • The method. An endpoint that rejects GET may accept POST, PUT, or the frequently-forgotten OPTIONS, which lists what else it takes.
  • Authorisation headers. Swap a token for another user’s and see what comes back - the whole of broken access control lives here.
  • Content-Type. The same body parsed as JSON versus form-encoded can reach entirely different code paths.
  • Redirect following. Turning it off shows you the 302 itself, including headers and body that a browser discards.

Related tools