HTTPie is a command line HTTP client, a user-friendly cURL replacement

#1

Post by grhmc » Fri, Jun 13, 2014, 7:14 PM UTC

HTTPie is a command line HTTP client, a user-friendly cURL replacement
httpie.org

Re: HTTPie is a command line HTTP client, a user-friendly cURL replacement

#2

Post by todd3834 » Fri, Jun 13, 2014, 7:27 PM UTC

At first I thought, what is so unfriendly about cURL? Then I saw the screenshot that shows a comparable cURL request behind the HTTPie request and I'm convinced.

Re: HTTPie is a command line HTTP client, a user-friendly cURL replacement

#3

Post by barosl » Fri, Jun 13, 2014, 7:36 PM UTC

Determining the type of an argument by looking up the presence of ':', '=', or '==' is brilliant. I liked it.

It can also be used to replace Wget, which not only breaks a multibyte filename sometimes, but also requires the --content-disposition option to handle the Content-Disposition header.

Re: HTTPie is a command line HTTP client, a user-friendly cURL replacement

#4

Post by halayli » Fri, Jun 13, 2014, 7:42 PM UTC

I'd just wrap a simple program around curl to improve its argument passing complexity if that's your pain point but I wouldn't go on rewriting an HTTP client.

Curl is a very mature code base by now and that's something to appreciate. It handles all the edge cases well and has dealt with all the mess that you'll discover over time.

Re: HTTPie is a command line HTTP client, a user-friendly cURL replacement

#5

Post by _nullandnull_ » Fri, Jun 13, 2014, 7:44 PM UTC

Poor choice of name. All I can see is HTTP Internet Explorer.

Re: HTTPie is a command line HTTP client, a user-friendly cURL replacement

#6

Post by jabagonuts » Fri, Jun 13, 2014, 7:44 PM UTC

todd3834 wrote: post #2

At first I thought, what is so unfriendly about cURL? Then I saw the screenshot that shows a comparable cURL request behind the HTTPie request and I'm convinced.

That was my first thought, too. Then I saw the colorized output and I'm convinced, too.

Re: HTTPie is a command line HTTP client, a user-friendly cURL replacement

#7

Post by jfe » Fri, Jun 13, 2014, 7:53 PM UTC

_nullandnull_ wrote: post #5

Poor choice of name. All I can see is HTTP Internet Explorer.

ditto. HTTPy would have been better, methinks.

Re: HTTPie is a command line HTTP client, a user-friendly cURL replacement

#8

Post by lukasm » Fri, Jun 13, 2014, 7:53 PM UTC

Instead of curl I was usually writing https://github.com/kennethreitz/requests

Re: HTTPie is a command line HTTP client, a user-friendly cURL replacement

#9

Post by laurent123456 » Fri, Jun 13, 2014, 7:59 PM UTC

jabagonuts wrote: post #6

todd3834 wrote: post #2

At first I thought, what is so unfriendly about cURL? Then I saw the screenshot that shows a comparable cURL request behind the HTTPie request and I'm convinced.

That was my first thought, too. Then I saw the colorized output and I'm convinced, too.

Isn't the HTTpie command simpler because it uses defaults for the content type and charset? If Curl did the same (not sure why it should because not everything is JSON/UTF-8), the command would be about as short as the HTTPie one.

Re: HTTPie is a command line HTTP client, a user-friendly cURL replacement

#10

Post by paulannesley » Fri, Jun 13, 2014, 7:59 PM UTC

halayli wrote: post #4

I'd just wrap a simple program around curl to improve its argument passing complexity if that's your pain point but I wouldn't go on rewriting an HTTP client. Curl is a very mature code base by now and that's something to appreciate. It handles all the edge cases well and has dealt with all the mess that you'll discover over time.

httpie uses requests[0] under the hood, a well respected python HTT library. See https://github.com/jakubroztocil/httpie/blob/77955c9837259b1...