Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

HTTPie: a CLI, cURL-like tool for humans

github.com

Post reply on HN
Print view View original

31–40 of 53 posts

Re: HTTPie: a CLI, cURL-like tool for humans

#31

Post by dperfect »

dordoka wrote: post #27
alayne wrote: post #23

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. Is there anything similar for GUI users? The st…

If you are on OS X, you should try Paw [0]. It's like Postman but with native GUI and lots of options. I use it everyday. [0] https://luckymarmot.com/paw

Paw is really nice. I love that you can string together multiple requests with "dynamic values" (connecting the output from one request to the inputs of another, with transformations/functions/whatever). I use the command line for a lot of things, but Charles + Paw is a super powerful combination for tinkering with HTTP requests outside of code.

Re: HTTPie: a CLI, cURL-like tool for humans

#32

Post by paulannesley »

I like using HTTPie for many things, however the current release does a bad job of rendering XML, e.g. it'll display ``" rel="nofollow">http://…">` as ``" rel="nofollow">http://…">`. But — I just checked and found the not-yet-released v1.0.0 fixes this by removing the XML formatter completely as discussed in https://github.com/jkbrzt/httpie/issues/443 so my gripe is sorted.

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.

Re: HTTPie: a CLI, cURL-like tool for humans

#33

Post by pbreit »

alayne wrote: post #23

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. Is there anything similar for GUI users? The st…

Have you tried Postman? Does it not do what you'd like.

Re: HTTPie: a CLI, cURL-like tool for humans

#35

Post by scrollaway »

peterwwillis wrote: post #29
scrollaway wrote: post #12

Earlier quoted context omitted.

I think I understand what you're saying, but all it would be is a change of ownership/packaging. httpie is only an interface to lower level libraries which already exist (requests and therefore urllib3). Whether it's an interface to requests or to libcurl matters fairly little. It'd be quite a drag if it were to libcurl in fact because syntax highlighting would be a lot harder, for example.

"all it would be" is a gigantic wealth of new functionality that requests/urllib3 does not have (compare libcurl and urllib3 features), along with greater support, developer base, test coverage, user base, and lower tco. httpie gains a wealth of advantages and cURL gets syntax highlighting. It's hard to overstate how advantageous to httpie it would be.

You are extremely confused at which level it is beneficial to merge projects.

You don't simplify things by going from one popular lib to another, especially when they both have legitimate use cases. Requests is one of Python's most highly regarded libs and a very popular one at that. Httpie is not its only user.

And what you are describing is not a simple process. Gaining tests and features (what features anyway?) is not good enough for it.

Re: HTTPie: a CLI, cURL-like tool for humans

#36

Post by jkbr »

alayne wrote: post #23

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. Is there anything similar for GUI users? The st…

Do you have an example of a request that you're unable to make with HTTPie?

Re: HTTPie: a CLI, cURL-like tool for humans

#38

Post by zymhan »

gamedna wrote: post #22

First off, I am really surprised how often this gets re-posted to HN. https://hn.algolia.com/?query=httpie&sort=byPopularity&prefi... I discovered HTTPie a few years back and it has completely replaced curl/wget during our API development and testing.

I guess it's still growing in popularity but hasn't hit the inflection point of becoming a standard tool.

The concept of an HTTP CLI seems obvious to me in retrospect, but I'm not a web developer, so maybe there's a reason this isn't as useful it would seem at first glance?

Re: HTTPie: a CLI, cURL-like tool for humans

#39

Post by Sir_Cmpwn »

agumonkey wrote: post #37
gamedna wrote: post #25

Forgot to mention that when dealing with JSON APIs, httpie + jq is a killer combo. https://stedolan.github.io/jq/

Reading the docs will probably make people feel all kinds of feelings. Especially the `last` part.

I don't understand. `echo '[1,2,3,4]' | jq last` seems pretty straightforward to me and so are the docs.

Re: HTTPie: a CLI, cURL-like tool for humans

#40

Post by agumonkey »

Sir_Cmpwn wrote: post #39
agumonkey wrote: post #37

Earlier quoted context omitted.

Reading the docs will probably make people feel all kinds of feelings. Especially the `last` part.

I don't understand. `echo '[1,2,3,4]' | jq last` seems pretty straightforward to me and so are the docs.

I was punning on the fact that the last part of jq's documentation introduces an almost full fledged functional programming language with function definition, map etc etc
Post reply on HN