I've been using HTTPie a lot more recently. It really takes the tedium out of using curl and I can produce color coded output for people. However, I am still finding myself in situations where I can't figure out how to induce the correct request. In other words, the user friendliness of being able to do things like construct JSON from parameters is great until it isn't.<p>Is there anything similar for GUI users? The standalone application form of Postman is popular with some coworkers for general HTTP work as is Fiddler on Windows.
First off, I am really surprised how often this gets re-posted to HN. <a href="https://hn.algolia.com/?query=httpie&sort=byPopularity&prefix&page=0&dateRange=all&type=story" rel="nofollow">https://hn.algolia.com/?query=httpie&sort=byPopularity&prefi...</a><p>I discovered HTTPie a few years back and it has completely replaced curl/wget during our API development and testing.
Forgot to mention that when dealing with JSON APIs, httpie + jq is a killer combo.<p><a href="https://stedolan.github.io/jq/" rel="nofollow">https://stedolan.github.io/jq/</a>
I really like this because by default it gives all of the http headers and makes everything look really nice. Curl still has its place, and I wouldn't dream of replacing it, but I would definitely use this as a sort of command line shortcut. Cool project.
Previously discussed at <a href="https://news.ycombinator.com/item?id=10418882" rel="nofollow">https://news.ycombinator.com/item?id=10418882</a>. More at <a href="https://hn.algolia.com/?query=HTTPie%20points%3E5&sort=byDate&dateRange=all&type=story&storyText=false&prefix&page=0" rel="nofollow">https://hn.algolia.com/?query=HTTPie%20points%3E5&sort=byDat...</a>
There's also a nice auto-complete utility built on top of HTTPie:<p><a href="https://github.com/eliangcs/http-prompt" rel="nofollow">https://github.com/eliangcs/http-prompt</a>
I like using HTTPie for many things, however the current release does a bad job of rendering XML, e.g. it'll display `<sitemapindex xmlns="<a href="http://…">`" rel="nofollow">http://…">`</a> as `<ns0:sitemapindex xmlns:ns0="<a href="http://…">`" rel="nofollow">http://…">`</a>. But — I just checked and found the not-yet-released v1.0.0 fixes this by removing the XML formatter completely as discussed in <a href="https://github.com/jkbrzt/httpie/issues/443" rel="nofollow">https://github.com/jkbrzt/httpie/issues/443</a> so my gripe is sorted.<p>I still tend to go back to cURL when I want to see exactly what's been received, and use httpie for when I know the response headers and body serialization are fine and I want to see the data therein.
I keep switching between curl + jq vs httpie. Lately I've been using mostly httpie. It is a great tool. One of my favorite things is it builds json objects (say for 'put' and 'post' for example) using command line arguments. So can have:<p><pre><code> $ http put url key1=val1 key2=val2
</code></pre>
If one of the fields is a larger nested object can use :=<p><pre><code> $ http put url key1=simpleval1 key2:='{literaljson...}'</code></pre>
I don't use this kind of programs all the time (but I did last week) so I eventually forget that I installed httpie and end up using curl or wget. I should alias curl to httpie and use \curl for when I really need curl.