5 ms·
Nice. Ignore the haters, this is a wonderful _companion_ to curl. As others noted, I'd revert to curl commands for sharing with others (or for performance-sens
by rodw 11y ago
Nice. Ignore the haters, this is a wonderful _companion_ to curl.
As others noted, I'd revert to curl commands for sharing with others (or for performance-sensitive tasks like downloads or quick-and-dirty load generation) but this may become my go-to HTTP CLI for personal use -- if only because it looks like won't need to look at the man page every time I want to do much more than a basic curl -X <METHOD> <URL>. (But maybe that says more about me than curl/httpie.)
One neat feature to add would be a mode that accepts the curl syntax (or at least the common parts of it), that way all the curl examples and "Copy as curl" tools work with httpie as well.
Conversely, an option that accepts httpie syntax and outputs the corresponding curl command might be convenient as well. (But I guess at that point maybe httpie devolves into a command-line parser + pretty-printer that wraps around curl, but that may not be all bad either.)
- chrstphrhrt 11y agoI like using httpie for documentation, tutorials and blog posts because I feel it is more readable. I also really like how you can skip the whole "http://localhost/" http://localhost/" bit for local development. Just "http :9200" for elasticsearch, "http :6543" for pyramid etc. Agreed that curl is good for things that should be copied and pasted directly or for matters of distribution because it is guaranteed to be installed everywhere. Would also love a httpie2curl converter for those times when testing in httpie and needing to distribute the requests to places without it.
- nerdwaller 11y agoI used to use this pretty frequently at a previous job that had a weird login flow. The nice part about httpie is the custom authorization implementations (verses chaining a bunch of curl/awk/sed calls to do the flow). But I fully agree, it's a complement.