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

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

httpie.org

Post reply on HN
Print view View original

41–50 of 79 posts

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

#41

Post by 13throwaway »

aleem wrote: post #33
suprgeek wrote: post #17

This is one of the little known gems I recommend often. the readability difference is just amazing for me. On that note for those of us having to use Windows at the workplace there are a few things that make life easier: 1) Chocolatey (package manager) 2) HTTPie 3) ConEmu (Shell) 4) gow (Unix command line utilities in Windows) 5) WinMerge (win diff) 6) TortiseSVN 7) SourceTree (git) Makes day to day stuff much smooth…

I have moved away from windows and miss Fiddler the most. It's ability to record, filter, edit and replay requests made debugging a breeze.

I like Mitmproxy. http://mitmproxy.org

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

#43

Post by pcunite »

suprgeek wrote: post #17

This is one of the little known gems I recommend often. the readability difference is just amazing for me. On that note for those of us having to use Windows at the workplace there are a few things that make life easier: 1) Chocolatey (package manager) 2) HTTPie 3) ConEmu (Shell) 4) gow (Unix command line utilities in Windows) 5) WinMerge (win diff) 6) TortiseSVN 7) SourceTree (git) Makes day to day stuff much smooth…

8) FileSearchEX for searching through source code files

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

#44

Post by Franciscouzo »

zhng wrote: post #40
diminoten wrote: post #31

Earlier quoted context omitted.

Requests does use an ordered dictionary for handling headers.

It should as order is important.

www.ietf.org/rfc/rfc2616.txt

4.2 Message Headers

The order in which header fields with differing field names are received is not significant. However, it is "good practice" to send general-header fields first, followed by request-header or response-header fields, and ending with the entity-header fields.

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

#45

Post by 0xhex »

diminoten wrote: post #31
jacquesm wrote: post #21

Earlier quoted context omitted.

That would appear to be a bug to me. When you want to see the headers of such a transaction you want to see them in the order in which they left the server. I checked the server and it looks like CURL has it right. Colorizing is one thing, reordering is quite another, debugging tools should show the situation with as much fidelity as possible.

Requests does use an ordered dictionary for handling headers.

Requests might but that's irrelevant. Requests is built on top of urllib3 which is built on top of httplib which does use a plain dict. Also the relevant RFC says order is irrelevant.

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

#46

Post by vdaniuk »

positr0n wrote: post #37
suprgeek wrote: post #17

This is one of the little known gems I recommend often. the readability difference is just amazing for me. On that note for those of us having to use Windows at the workplace there are a few things that make life easier: 1) Chocolatey (package manager) 2) HTTPie 3) ConEmu (Shell) 4) gow (Unix command line utilities in Windows) 5) WinMerge (win diff) 6) TortiseSVN 7) SourceTree (git) Makes day to day stuff much smooth…

You (and anyone reading this great list of recommendations) should try cmder. It's a customized build of ConEmu with lots of goodies thrown in. http://bliker.github.io/cmder/

Can confirm, cmder is great, it makes console use on Windows bearable.

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

#47

Post by throwaway5752 »

Franciscouzo wrote: post #44
zhng wrote: post #40

Earlier quoted context omitted.

It should as order is important.

www.ietf.org/rfc/rfc2616.txt 4.2 Message Headers The order in which header fields with differing field names are received is not significant. However, it is "good practice" to send general-header fields first, followed by request-header or response-header fields, and ending with the entity-header fields.

Yes, if you're implementing a client or server, you should not depend on the order of the headers. Completely separately, when I have a command line client for debugging, I want to see the request and response exactly as they were sent/received, respectively.

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

#49

Post by rat87 »

mariusmg wrote: post #30
suprgeek wrote: post #17

This is one of the little known gems I recommend often. the readability difference is just amazing for me. On that note for those of us having to use Windows at the workplace there are a few things that make life easier: 1) Chocolatey (package manager) 2) HTTPie 3) ConEmu (Shell) 4) gow (Unix command line utilities in Windows) 5) WinMerge (win diff) 6) TortiseSVN 7) SourceTree (git) Makes day to day stuff much smooth…

WinMerge is not that good. BeyondCompare is in a league of it's own when it comes with diff apps (it's commercial though). I can vouch for the rest too....ConEmu especially is very very nice.

I've had it installed on a bunch of corporate boxes and never used it and I'm not sure if anyone used it.

Even though it's a bit crash happy on windows and the gtk file picker sucks on windows for my uses meld was the most useful(at least now they have a packaged version for windows - http://sourceforge.net/projects/meld-installer/ - so you don't have to package it yourself). It's simple, good looking, highlights the difference between 2 slightly modified lines, has support for comparing directories, and allows in-place editing.

Post reply on HN