About HTTP Request Replayer

Generate fetch/axios/curl code from raw HTTP request text. Part of the DevTools Surf developer suite. Browse more tools in the Developer Utilities collection.

Use Cases

• Developers reproducing bugs from raw HTTP request logs
• QA engineers converting captured requests into automated test scripts
• Security testers replaying modified requests for penetration testing
• API debuggers generating shareable reproduction steps from traffic

Tips

• Paste raw HTTP requests from browser DevTools network tab
• Choose between fetch, axios, or curl output formats
• Include headers and body to generate complete replay code

Fun Facts

• The curl command-line tool was first released by Daniel Stenberg in 1998 and now runs on over 10 billion installations worldwide, including cars, TVs, and game consoles.
• The Fetch API was introduced in 2015 as a modern replacement for XMLHttpRequest — unlike XHR, it uses Promises and was designed by the WHATWG rather than the W3C.
• Axios, created by Matt Zabriskie in 2014, became the most popular HTTP client library on npm by offering automatic JSON parsing and request interception that fetch lacked.

FAQ

What's 'raw HTTP request' format?

The wire format: `POST /api HTTP/1.1\nHost: ...\nContent-Type: ...\n\n{body}`. What you see in Wireshark or browser 'Copy as raw'.

Why replay?

Reproducing customer issues, testing a failing request locally, or converting a network capture into code for automated retries.

Does it preserve all headers?

Yes — including ones fetch would set automatically (User-Agent, Accept). Toggle to exclude browser-default headers if you want a minimal equivalent.

What about WebSocket upgrades?

HTTP requests only. WebSocket handshakes are specialized — the tool flags them and suggests a WS-specific replayer.