5 ms·

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.

• amjd 12y ago
  Httpie doesn't come close to Curl in terms of features. Its selling points are colourised output (using pygments) and (slightly) better json formatting. Here's an unobstructed side by side comparison for the same request: http://i.imgur.com/Bj2wRkq.png http://i.imgur.com/Bj2wRkq.png While it won't replace Curl, it can prove quite useful while testing APIs.
  • jacquesm 12y ago
    Why is the order of the headers different between those two examples?
    • notdonspaulding 12y ago
      I haven't looked at any code, but I would strongly suspect that it's because either HTTPie or python-requests is using a plain dictionary instead of an ordered dictionary under the hood.
      • jacquesm 12y ago
        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.
        • diminoten 12y ago
          Requests does use an ordered dictionary for handling headers.
          • zhng 12y ago
            It should as order is important.
            • Franciscouzo 12y ago
              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.
              • throwaway5752 12y ago
                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.
              • zhng 12y ago
                > Instances of the same path and name will overwrite each other, with the latest instance taking precedence. Instances of the same path but different names will add additional mappings. > When sending cookies to a server, all cookies with a more specific path mapping should be sent before cookies with less specific path mappings. For example, a cookie "name1=foo" with a path mapping of "/" should be sent after a cookie "name1=foo2" with a path mapping of "/bar" if they are both to be sent. http://curl.haxx.se/rfc/cookie_spec.html http://curl.haxx.se/rfc/cookie_spec.html
          • 0xhex 12y ago
            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.
    • anonova 12y ago
      HTTPie sorts them before outputted. In the readme: https://github.com/jakubroztocil/httpie#colors-and-formatting https://github.com/jakubroztocil/httpie#colors-and-formattin... In the code: https://github.com/jakubroztocil/httpie/blob/master/httpie/output/formatters/headers.py https://github.com/jakubroztocil/httpie/blob/master/httpie/o...
  • sethammons 12y ago
    The user agent is truncated in HTTPie.
• paulannesley 12y ago
  httpie uses requests[0] under the hood, a well respected python HTT library. See https://github.com/jakubroztocil/httpie/blob/77955c9837259b1159e87d4a47bd67d47b1c7d6d/setup.py#L32 https://github.com/jakubroztocil/httpie/blob/77955c9837259b1...
• jayd16 12y ago
  Exactly. Seems like a lot of the verbosity that is saved is simply implicitly assuming -i -H 'Content-Type: application/json; charset=utf-8'