[halpert]

Doesn’t curl do this just as easily?

[IshKebab]

Sounds a lot easier than curl tbh. No need to deal with shell scripts and their insane quoting, plus you get the response straight in your editor with syntax highlighting.

[halpert]

Maybe it’s just me but I’ve never had those issues. Another benefit of curl is that you have an easily searchable history of every command you’ve run. So you can easily find old invocations and rerun them.

[avel]

This extension also keeps a history of requests.

How complicated are your requests? If I need to test a POST request with a JSON payload longer than a line or two, I'll go and construct my curl command in a text editor anyway, since the shell prompt / readline is not easy to edit. Once you need to start escaping single or double quotes or html payloads in the request, it quickly gets cumbersome. At that point I ditch the shell as a middleman and use the editor to submit the request for me.

[halpert]

You can have curl read the request body from a file using --data @filename.txt.

[piaste]

Which means you've opened an editor already to edit the request. Might as well send the request right there via an editor command/plugin.

[halpert]

Or you saved the response from a different curl request, or it’s checked into git, or a million different reasons.