As easy as /aitch-tee-tee-pie/ 🥧 Modern, user-friendly command-line HTTP client for the API era. JSON support, colors, sessions, downloads, plugins & more.


HTTPie: human-friendly CLI HTTP client for the API era

HTTPie (pronounced aitch-tee-tee-pie) is a command-line HTTP client. Its goal is to make CLI interaction with web services as human-friendly as possible. HTTPie is designed for testing, debugging, and generally interacting with APIs & HTTP servers. The http & https commands allow for creating and sending arbitrary HTTP requests. They use simple and natural syntax and provide formatted and colorized output.

Stable documentation Latest version released on PyPi Build status of the master branch on Mac/Linux/Windows Test coverage Download count Chat on Discord

HTTPie in action


1   About this document

This documentation is best viewed at

You can select your corresponding HTTPie version as well as run examples directly from the browser using a embedded terminal.

If you are reading this on GitHub, then this text covers the current development version. You are invited to submit fixes and improvements to the the docs by editing README.rst.

2   Main features

  • Expressive and intuitive syntax
  • Formatted and colorized terminal output
  • Built-in JSON support
  • Forms and file uploads
  • HTTPS, proxies, and authentication
  • Arbitrary request data
  • Custom headers
  • Persistent sessions
  • Wget-like downloads
  • Linux, macOS and Windows support
  • Plugins
  • Documentation
  • Test coverage

HTTPie compared to cURL

3   Installation

3.1   macOS

On macOS, HTTPie can be installed via Homebrew (recommended):

$ brew install httpie

A MacPorts port is also available:

$ port install httpie

3.2   Linux

Most Linux distributions provide a package that can be installed using the system package manager, for example:

# Debian, Ubuntu, etc.
$ apt install httpie
# Fedora
$ dnf install httpie
# CentOS, RHEL, ...
$ yum install httpie
# Gentoo
$ emerge httpie
# Arch Linux
$ pacman -S httpie

3.3   Windows, etc.

A universal installation method (that works on Windows, Mac OS X, Linux, …, and always provides the latest version) is to use pip:

# Make sure we have an up-to-date version of pip and setuptools:
$ python -m pip install --upgrade pip setuptools

$ python -m pip install --upgrade httpie

(If pip installation fails for some reason, you can try easy_install httpie as a fallback.)

3.4   Python version

Python version 3.6 or greater is required.

3.5   Unstable version

You can also install the latest unreleased development version directly from the master branch on GitHub. It is a work-in-progress of a future stable release so the experience might be not as smooth.

Build status of the master branch on Mac/Linux/Windows

On macOS you can install it with Homebrew:

$ brew uninstall --force httpie
$ brew install --HEAD httpie

Otherwise with pip:

$ pip install --upgrade

Verify that now we have the current development version identifier with the -dev suffix, for example:

$ http --version
# 2.0.0-dev

4   Usage

Hello World:

$ https


$ http [flags] [METHOD] URL [ITEM [ITEM]]

See also http --help.

4.1   Examples

Custom HTTP method, HTTP headers and JSON data:

$ http PUT X-API-Token:123 name=John

Submitting forms:

$ http -f POST hello=World

See the request that is being sent using one of the output options:

$ http -v

Build and print a request without sending it using offline mode:

$ http --offline hello=offline

Use GitHub API to post a comment on an issue with authentication:

$ http -a USERNAME POST body='HTTPie is awesome! :heart:'

Upload a file using redirected input:

$ http < files/data.json

Download a file and save it via redirected output:

$ http > image.png

Download a file wget style:

$ http --download

Use named sessions to make certain aspects of the communication persistent between requests to the same host:

$ http --session=logged-in -a username:password API-Key:123
$ http --session=logged-in

Set a custom Host header to work around missing DNS records:

$ http localhost:8000

5   HTTP method

The name of the HTTP method comes right before the URL argument:

$ http DELETE

Which looks similar to the actual Request-Line that is sent:

DELETE /delete HTTP/1.1

When the METHOD argument is omitted from the command, HTTPie defaults to either GET (with no request data) or POST (with request data).

6   Request URL

The only information HTTPie needs to perform a request is a URL.

The default scheme is http:// and can be omitted from the argument:

$ http
# =>

HTTPie also installs an https executable, where the default scheme is https://:

$ https
# =>

6.1   Querystring parameters

If you find yourself manually constructing URLs with querystring parameters on the terminal, you may appreciate the param==value syntax for appending URL parameters.

With that, you don’t have to worry about escaping the & separators for your shell. Additionally, any special characters in the parameter name or value get automatically URL-escaped (as opposed to parameters specified in the full URL, which HTTPie doesn’t modify).

$ http q==httpie per_page==1
GET /search/repositories?q=httpie&per_page=1 HTTP/1.1

6.2   URL shortcuts for localhost

Additionally, curl-like shorthand for localhost is supported. This means that, for example :3000 would expand to http://localhost:3000 If the port is omitted, then port 80 is assumed.

$ http :/foo
GET /foo HTTP/1.1
Host: localhost
$ http :3000/bar
GET /bar HTTP/1.1
Host: localhost:3000
$ http :
GET / HTTP/1.1
Host: localhost

6.3   Other default schemes

When HTTPie is invoked as https then the default scheme is https:// ($ https will make a request to

You can also use the --default-scheme <URL_SCHEME> option to create shortcuts for other protocols than HTTP (possibly supported via plugins). Example for the httpie-unixsocket plugin:

# Before
$ http http+unix://%2Fvar%2Frun%2Fdocker.sock/info
# Create an alias
$ alias http-unix='http --default-scheme="http+unix"'
# Now the scheme can be omitted
$ http-unix %2Fvar%2Frun%2Fdocker.sock/info

6.4   --path-as-is

The standard behaviour of HTTP clients is to normalize the path portion of URLs by squashing dot segments as a typically filesystem would:

$ http -v
GET /etc/password HTTP/1.1

The --path-as-is option allows you to disable this behavior:

$ http --path-as-is -v
GET /../../etc/password HTTP/1.1

7   Request items

There are a few different request item types that provide a convenient mechanism for specifying HTTP headers, simple JSON and form data, files, and URL parameters.

They are key/value pairs specified after the URL. All have in common that they become part of the actual request that is sent and that their type is distinguished only by the separator used: :, =, :=, ==, @, [email protected], and :[email protected]. The ones with an @ expect a file path as value.

Item Type Description
HTTP Headers Name:Value Arbitrary HTTP header, e.g. X-API-Token:123.
URL parameters name==value Appends the given name/value pair as a query string parameter to the URL. The == separator is used.
Data Fields field=value, [email protected] Request data fields to be serialized as a JSON object (default), to be form-encoded (with --form, -f), or to be serialized as multipart/form-data (with --multipart).
Raw JSON fields field:=json, field:[email protected] Useful when sending JSON and one or more fields need to be a Boolean, Number, nested Object, or an Array, e.g., meals:='["ham","spam"]' or pies:=[1,2,3] (note the quotes).
Fields upload fields [email protected]/dir/file [email protected];type=mime Only available with --form, -f and --multipart. For example [email protected]~/Pictures/img.png, or '[email protected];type=text/markdown'. With --form, the presence of a file field results in a --multipart request.

Note that data fields aren’t the only way to specify request data: Redirected input is a mechanism for passing arbitrary request data.

7.1   Escaping rules

You can use \ to escape characters that shouldn’t be used as separators (or parts thereof). For instance, foo\==bar will become a data key/value pair (foo= and bar) instead of a URL parameter.

Often it is necessary to quote the values, e.g. foo='bar baz'.

If any of the field names or headers starts with a minus (e.g., -fieldname), you need to place all such items after the special token -- to prevent confusion with --arguments:

$ http  --  -name-starting-with-dash=foo -Unusual-Header:bar
POST /post HTTP/1.1
-Unusual-Header: bar
Content-Type: application/json

    "-name-starting-with-dash": "foo"

8   JSON

JSON is the lingua franca of modern web services and it is also the implicit content type HTTPie uses by default.

Simple example:

$ http PUT name=John [email protected]
PUT / HTTP/1.1
Accept: application/json, */*;q=0.5
Accept-Encoding: gzip, deflate
Content-Type: application/json

    "name": "John",
    "email": "[email protected]"

8.1   Default behaviour

If your command includes some data request items, they are serialized as a JSON object by default. HTTPie also automatically sets the following headers, both of which can be overwritten:

Content-Type application/json
Accept application/json, */*;q=0.5

8.2   Explicit JSON

You can use --json, -j to explicitly set Accept to application/json regardless of whether you are sending data (it’s a shortcut for setting the header via the usual header notation: http url Accept:'application/json, */*;q=0.5'). Additionally, HTTPie will try to detect JSON responses even when the Content-Type is incorrectly text/plain or unknown.

8.3   Non-string JSON fields

Non-string JSON fields use the := separator, which allows you to embed arbitrary JSON data into the resulting JSON object. Additionally, text and raw JSON files can also be embedded into fields using [email protected] and :[email protected]:

$ http PUT \
    name=John \                        # String (default)
    age:=29 \                          # Raw JSON — Number
    married:=false \                   # Raw JSON — Boolean
    hobbies:='["http", "pies"]' \      # Raw JSON — Array
    favorite:='{"tool": "HTTPie"}' \   # Raw JSON — Object
    bookmarks:[email protected]/data.json \      # Embed JSON file
    [email protected]/text.txt        # Embed text file
PUT /person/1 HTTP/1.1
Accept: application/json, */*;q=0.5
Content-Type: application/json

    "age": 29,
    "hobbies": [
    "description": "John is a nice guy who likes pies.",
    "married": false,
    "name": "John",
    "favorite": {
        "tool": "HTTPie"
    "bookmarks": {
        "HTTPie": "",

8.4   Raw and complex JSON

Please note that with the request items data field syntax, commands can quickly become unwieldy when sending complex structures. In such cases, it’s better to pass the full raw JSON data via redirected input, for example:

$ echo '{"hello": "world"}' | http POST
$ http POST < files/data.json

Furthermore, this syntax only allows you to send an object as the JSON document, but not an array, etc. Here, again, the solution is to use redirected input.

9   Forms

Submitting forms is very similar to sending JSON requests. Often the only difference is in adding the --form, -f option, which ensures that data fields are serialized as, and Content-Type is set to, application/x-www-form-urlencoded; charset=utf-8. It is possible to make form data the implicit content type instead of JSON via the config file.

9.1   Regular forms

$ http --form POST name='John Smith'
POST /post HTTP/1.1
Content-Type: application/x-www-form-urlencoded; charset=utf-8


9.2   File upload forms

If one or more file fields is present, the serialization and content type is multipart/form-data:

$ http -f POST name='John Smith' [email protected]~/files/data.xml

The request above is the same as if the following HTML form were submitted:

<form enctype="multipart/form-data" method="post" action="">
    <input type="text" name="name" />
    <input type="file" name="cv" />

Please note that @ is used to simulate a file upload form field, whereas [email protected] just embeds the file content as a regular text field value.

When uploading files, their content type is inferred from the file name. You can manually override the inferred content type:

$ http -f POST name='John Smith' [email protected]'~/files/data.bin;type=application/pdf'

To perform a multipart/form-data request even without any files, use --multipart instead of --form:

$ http --multipart --offline hello=world
Content-Length: 129
Content-Type: multipart/form-data; boundary=c31279ab254f40aeb06df32b433cbccb

Content-Disposition: form-data; name="hello"


File uploads are always streamed to avoid memory issues with large files.

By default, HTTPie uses a random unique string as the multipart boundary but you can use --boundary to specify a custom string instead:

$ http --form --multipart --boundary=xoxo --offline hello=world
Content-Length: 129
Content-Type: multipart/form-data; boundary=xoxo

Content-Disposition: form-data; name="hello"


If you specify a custom Content-Type header without including the boundary bit, HTTPie will add the boundary value (explicitly specified or auto-generated) to the header automatically:

http --form --multipart --offline hello=world Content-Type:multipart/letter
Content-Length: 129
Content-Type: multipart/letter; boundary=c31279ab254f40aeb06df32b433cbccb

Content-Disposition: form-data; name="hello"


10   HTTP headers

To set custom headers you can use the Header:Value notation:

$ http  User-Agent:Bacon/1.0  'Cookie:valued-visitor=yes;foo=bar'  \
    X-Foo:Bar  Referer:
GET /headers HTTP/1.1
Accept: */*
Accept-Encoding: gzip, deflate
Cookie: valued-visitor=yes;foo=bar
User-Agent: Bacon/1.0
X-Foo: Bar

10.1   Default request headers

There are a couple of default headers that HTTPie sets:

GET / HTTP/1.1
Accept: */*
Accept-Encoding: gzip, deflate
User-Agent: HTTPie/<version>
Host: <taken-from-URL>

Any of these can be overwritten and some of them unset (see below).

10.2   Empty headers and header un-setting

To unset a previously specified header (such a one of the default headers), use Header::

$ http Accept: User-Agent:

To send a header with an empty value, use Header;:

$ http 'Header;'

10.3   Limiting response headers

The --max-headers=n options allows you to control the number of headers HTTPie reads before giving up (the default 0, i.e., there’s no limit).

$ http --max-headers=100

11   Offline mode

Use --offline to construct HTTP requests without sending them anywhere. With --offline, HTTPie builds a request based on the specified options and arguments, prints it to stdout, and then exits. It works completely offline; no network connection is ever made. This has a number of use cases, including:

Generating API documentation examples that you can copy & paste without sending a request:

$ http --offline POST server.chess/api/games API-Key:ZZZ w=magnus b=hikaru t=180 i=2
$ http --offline MOVE server.chess/api/games/123 API-Key:ZZZ p=b a=R1a3 t=77

Generating raw requests that can be sent with any other client:

# 1. save a raw request to a file:
$ http --offline POST hello=world > request.http
# 2. send it over the wire with, for example, the fantastic netcat tool:
$ nc 80 < request.http

You can also use the --offline mode for debugging and exploring HTTP and HTTPie, and for “dry runs”.

--offline has the side-effect of automatically activating --print=HB, i.e., both the request headers and the body are printed. You can customize the output with the usual output options, with the exception that there is not response to be printed. You can use --offline in combination with all the other options (e.g., --session).

12   Cookies

HTTP clients send cookies to the server as regular HTTP headers. That means, HTTPie does not offer any special syntax for specifying cookies — the usual Header:Value notation is used:

Send a single cookie:

$ http Cookie:sessionid=foo
GET / HTTP/1.1
Accept: */*
Accept-Encoding: gzip, deflate
Connection: keep-alive
Cookie: sessionid=foo
User-Agent: HTTPie/0.9.9

Send multiple cookies (note the header is quoted to prevent the shell from interpreting the ;):

$ http 'Cookie:sessionid=foo;another-cookie=bar'
GET / HTTP/1.1
Accept: */*
Accept-Encoding: gzip, deflate
Connection: keep-alive
Cookie: sessionid=foo;another-cookie=bar
User-Agent: HTTPie/0.9.9

If you often deal with cookies in your requests, then chances are you’d appreciate the sessions feature.

13   Authentication

The currently supported authentication schemes are Basic and Digest (see auth plugins for more). There are two flags that control authentication:

--auth, -a Pass a username:password pair as the argument. Or, if you only specify a username (-a username), you’ll be prompted for the password before the request is sent. To send an empty password, pass username:. The username:[email protected] URL syntax is supported as well (but credentials passed via -a have higher priority).
--auth-type, -A Specify the auth mechanism. Possible values are basic, digest, or the name of any auth plugins you have installed. The default value is basic so it can often be omitted.

13.1   Basic auth

$ http -a username:password

13.2   Digest auth

$ http -A digest -a username:password

13.3   Password prompt

$ http -a username

13.4   Empty password

$ http -a username:

13.5   .netrc

Authentication information from your ~/.netrc file is by default honored as well.

For example:

$ cat ~/.netrc
login httpie
password test
$ http
HTTP/1.1 200 OK

This can be disabled with the --ignore-netrc option:

$ http --ignore-netrc

13.6   Auth plugins

Additional authentication mechanism can be installed as plugins. They can be found on the Python Package Index. Here’s a few picks:

14   HTTP redirects

By default, HTTP redirects are not followed and only the first response is shown:

$ http

14.1   Follow Location

To instruct HTTPie to follow the Location header of 30x responses and show the final response instead, use the --follow, -F option:

$ http --follow

14.2   Showing intermediary redirect responses

If you additionally wish to see the intermediary requests/responses, then use the --all option as well:

$ http --follow --all

14.3   Limiting maximum redirects followed

To change the default limit of maximum 30 redirects, use the --max-redirects=<limit> option:

$ http --follow --all --max-redirects=2

15   Proxies

You can specify proxies to be used through the --proxy argument for each protocol (which is included in the value in case of redirects across protocols):

$ http --proxy=http: --proxy=https:

With Basic authentication:

$ http --proxy=http:http://user:[email protected]:3128

15.1   Environment variables

You can also configure proxies by environment variables ALL_PROXY, HTTP_PROXY and HTTPS_PROXY, and the underlying Requests library will pick them up as well. If you want to disable proxies configured through the environment variables for certain hosts, you can specify them in NO_PROXY.

In your ~/.bash_profile:

export HTTP_PROXY=
export NO_PROXY=localhost,

15.2   SOCKS

Usage is the same as for other types of proxies:

$ http --proxy=http:socks5://user:[email protected]:port --proxy=https:socks5://user:[email protected]:port

16   HTTPS

16.1   Server SSL certificate verification

To skip the host’s SSL certificate verification, you can pass --verify=no (default is yes):

$ http --verify=no

16.2   Custom CA bundle

You can also use --verify=<CA_BUNDLE_PATH> to set a custom CA bundle path:

$ http --verify=/ssl/custom_ca_bundle

16.3   Client side SSL certificate

To use a client side certificate for the SSL communication, you can pass the path of the cert file with --cert:

$ http --cert=client.pem

If the private key is not contained in the cert file you may pass the path of the key file with --cert-key:

$ http --cert=client.crt --cert-key=client.key

16.4   SSL version

Use the --ssl=<PROTOCOL> option to specify the desired protocol version to use. This will default to SSL v2.3 which will negotiate the highest protocol that both the server and your installation of OpenSSL support. The available protocols are ssl2.3, ssl3, tls1, tls1.1, tls1.2, tls1.3. (The actually available set of protocols may vary depending on your OpenSSL installation.)

# Specify the vulnerable SSL v3 protocol to talk to an outdated server:
$ http --ssl=ssl3

16.5   SSL ciphers

You can specify the available ciphers with --ciphers. It should be a string in the OpenSSL cipher list format.

$ http --ciphers=ECDHE-RSA-AES128-GCM-SHA256

Note: these cipher strings do not change the negotiated version of SSL or TLS, they only affect the list of available cipher suites.

To see the default cipher string, run http --help and see the --ciphers section under SSL.

17   Output options

By default, HTTPie only outputs the final response and the whole response message is printed (headers as well as the body). You can control what should be printed via several options:

--headers, -h Only the response headers are printed.
--body, -b Only the response body is printed.
--verbose, -v Print the whole HTTP exchange (request and response). This option also enables --all (see below).
--print, -p Selects parts of the HTTP exchange.
--quiet, -q Don't print anything to stdout and stderr.

17.1   What parts of the HTTP exchange should be printed

All the other output options are under the hood just shortcuts for the more powerful --print, -p. It accepts a string of characters each of which represents a specific part of the HTTP exchange:

Character Stands for
H request headers
B request body
h response headers
b response body

Print request and response headers:

$ http --print=Hh PUT hello=world

17.2   Verbose output

--verbose can often be useful for debugging the request and generating documentation examples:

$ http --verbose PUT hello=world
PUT /put HTTP/1.1
Accept: application/json, */*;q=0.5
Accept-Encoding: gzip, deflate
Content-Type: application/json
User-Agent: HTTPie/0.2.7dev

    "hello": "world"

HTTP/1.1 200 OK
Connection: keep-alive
Content-Length: 477
Content-Type: application/json
Date: Sun, 05 Aug 2012 00:25:23 GMT
Server: gunicorn/0.13.4


17.3   Quiet output

--quiet redirects all output that would otherwise go to stdout and stderr to /dev/null (except for errors and warnings). This doesn’t affect output to a file via --output or --download.

# There will be no output:
$ http --quiet enjoy='the silence'

17.4   Viewing intermediary requests/responses

To see all the HTTP communication, i.e. the final request/response as well as any possible intermediary requests/responses, use the --all option. The intermediary HTTP communication include followed redirects (with --follow), the first unauthorized request when HTTP digest authentication is used (--auth=digest), etc.

# Include all responses that lead to the final one:
$ http --all --follow

The intermediary requests/response are by default formatted according to --print, -p (and its shortcuts described above). If you’d like to change that, use the --history-print, -P option. It takes the same arguments as --print, -p but applies to the intermediary requests only.

# Print the intermediary requests/responses differently than the final one:
$ http -A digest -a foo:bar --all -p Hh -P H

17.5   Conditional body download

As an optimization, the response body is downloaded from the server only if it’s part of the output. This is similar to performing a HEAD request, except that it applies to any HTTP method you use.

Let’s say that there is an API that returns the whole resource when it is updated, but you are only interested in the response headers to see the status code after an update:

$ http --headers PATCH name='New Name'

Since we are only printing the HTTP headers here, the connection to the server is closed as soon as all the response headers have been received. Therefore, bandwidth and time isn’t wasted downloading the body which you don’t care about. The response headers are downloaded always, even if they are not part of the output

18   Redirected Input

The universal method for passing request data is through redirected stdin (standard input)—piping.

By default, stdin data is buffered and then with no further processing used as the request body. If you provide Content-Length, then the request body is streamed without buffering. You can also use --chunked to enable streaming via chunked transfer encoding.

There are multiple useful ways to use piping:

Redirect from a file:

$ http PUT X-API-Token:123 < files/data.json

Or the output of another program:

$ grep '401 Unauthorized' /var/log/httpd/error_log | http POST

You can use echo for simple data:

$ echo '{"name": "John"}' | http PATCH X-API-Token:123

You can also use a Bash here string:

$ http <<<'{"name": "John"}'

You can even pipe web services together using HTTPie:

$ http GET | http POST

You can use cat to enter multiline data on the terminal:

$ cat | http POST
$ cat | http POST Content-Type:text/plain
- buy milk
- call parents

On OS X, you can send the contents of the clipboard with pbpaste:

$ pbpaste | http PUT

Passing data through stdin cannot be combined with data fields specified on the command line:

$ echo 'data' | http POST more=data   # This is invalid

To prevent HTTPie from reading stdin data you can use the --ignore-stdin option.

18.1   Request data from a filename

An alternative to redirected stdin is specifying a filename (as @/path/to/file) whose content is used as if it came from stdin.

It has the advantage that the Content-Type header is automatically set to the appropriate value based on the filename extension. For example, the following request sends the verbatim contents of that XML file with Content-Type: application/xml:

$ http PUT @files/data.xml

File uploads are always streamed to avoid memory issues with large files.

19   Chunked transfer encoding

You can use the --chunked flag to instruct HTTPie to use Transfer-Encoding: chunked:

$ http --chunked PUT hello=world
$ http --chunked --multipart PUT hello=world [email protected]/data.xml
$ http --chunked @files/data.xml
$ cat files/data.xml | http --chunked

20   Terminal output

HTTPie does several things by default in order to make its terminal output easy to read.

20.1   Colors and formatting

Syntax highlighting is applied to HTTP headers and bodies (where it makes sense). You can choose your preferred color scheme via the --style option if you don’t like the default one. There dozens of styles available, here are just a few special or notable ones:

auto Follows your terminal ANSI color styles. This is the default style used by HTTPie.
default Default styles of the underlying Pygments library. Not actually used by default by HTTPie. You can enable it with --style=default
monokai A popular color scheme. Enable with --style=monokai.
fruity A bold, colorful scheme. Enable with --style=fruity.
See $ http --help for all the possible --style values.

Also, the following formatting is applied:

  • HTTP headers are sorted by name.
  • JSON data is indented, sorted by keys, and unicode escapes are converted to the characters they represent.

One of these options can be used to control output processing:

--pretty=all Apply both colors and formatting. Default for terminal output.
--pretty=colors Apply colors.
--pretty=format Apply formatting.
--pretty=none Disables output processing. Default for redirected output.

You can control the applied formatting via the --format-options option. The following options are available:

For example, this is how you would disable the default header and JSON key sorting, and specify a custom JSON indent size:

$ http --format-options headers.sort:false,json.sort_keys:false,json.indent:2

This is something you will typically store as one of the default options in your config file. See http --help for all the available formatting options.

There are also two shortcuts that allow you to quickly disable and re-enable sorting-related format options (currently it means JSON keys and headers): --unsorted and --sorted.

20.2   Binary data

Binary data is suppressed for terminal output, which makes it safe to perform requests to URLs that send back binary data. Binary data is suppressed also in redirected, but prettified output. The connection is closed as soon as we know that the response body is binary,

$ http

You will nearly instantly see something like this:

HTTP/1.1 200 OK
Content-Type: application/octet-stream

| NOTE: binary data not shown in terminal |

21   Redirected output

HTTPie uses a different set of defaults for redirected output than for terminal output. The differences being:

  • Formatting and colors aren’t applied (unless --pretty is specified).
  • Only the response body is printed (unless one of the output options is set).
  • Also, binary data isn’t suppressed.

The reason is to make piping HTTPie’s output to another programs and downloading files work with no extra flags. Most of the time, only the raw response body is of an interest when the output is redirected.

Download a file:

$ http > image.png

Download an image of Octocat, resize it using ImageMagick, upload it elsewhere:

$ http | convert - -resize 25% -  | http

Force colorizing and formatting, and show both the request and the response in less pager:

$ http --pretty=all --verbose | less -R

The -R flag tells less to interpret color escape sequences included HTTPie`s output.

You can create a shortcut for invoking HTTPie with colorized and paged output by adding the following to your ~/.bash_profile:

function httpless {
    # `httpless'
    http --pretty=all --print=hb "[email protected]" | less -R;

22   Download mode

HTTPie features a download mode in which it acts similarly to wget.

When enabled using the --download, -d flag, response headers are printed to the terminal (stderr), and a progress bar is shown while the response body is being saved to a file.

$ http --download
HTTP/1.1 200 OK
Content-Disposition: attachment; filename=httpie-master.tar.gz
Content-Length: 257336
Content-Type: application/x-gzip

Downloading 251.30 kB to "httpie-master.tar.gz"
Done. 251.30 kB in 2.73862s (91.76 kB/s)

22.1   Downloaded filename

There are three mutually exclusive ways through which HTTPie determines the output filename (with decreasing priority):

  1. You can explicitly provide it via --output, -o. The file gets overwritten if it already exists (or appended to with --continue, -c).
  2. The server may specify the filename in the optional Content-Disposition response header. Any leading dots are stripped from a server-provided filename.
  3. The last resort HTTPie uses is to generate the filename from a combination of the request URL and the response Content-Type. The initial URL is always used as the basis for the generated filename — even if there has been one or more redirects.

To prevent data loss by overwriting, HTTPie adds a unique numerical suffix to the filename when necessary (unless specified with --output, -o).

22.2   Piping while downloading

You can also redirect the response body to another program while the response headers and progress are still shown in the terminal:

$ http -d |  tar zxf -

22.3   Resuming downloads

If --output, -o is specified, you can resume a partial download using the --continue, -c option. This only works with servers that support Range requests and 206 Partial Content responses. If the server doesn’t support that, the whole file will simply be downloaded:

$ http -dco

22.4   Other notes

  • The --download option only changes how the response body is treated.
  • You can still set custom headers, use sessions, --verbose, -v, etc.
  • --download always implies --follow (redirects are followed).
  • --download also implies --check-status (error HTTP status will result in a non-zero exist static code).
  • HTTPie exits with status code 1 (error) if the body hasn’t been fully downloaded.
  • Accept-Encoding cannot be set with --download.

23   Streamed responses

Responses are downloaded and printed in chunks which allows for streaming and large file downloads without using too much memory. However, when colors and formatting is applied, the whole response is buffered and only then processed at once.

23.1   Disabling buffering

You can use the --stream, -S flag to make two things happen:

  1. The output is flushed in much smaller chunks without any buffering, which makes HTTPie behave kind of like tail -f for URLs.
  2. Streaming becomes enabled even when the output is prettified: It will be applied to each line of the response and flushed immediately. This makes it possible to have a nice output for long-lived requests, such as one to the Twitter streaming API.

23.2   Examples use cases

Prettified streamed response:

$ http --stream

Streamed output by small chunks à la tail -f:

# Send each new line (JSON object) to another URL as soon as it arrives from a streaming API:
$ http --stream | while read line; do echo "$line" | http ; done

24   Sessions

By default, every request HTTPie makes is completely independent of any previous ones to the same host.

However, HTTPie also supports persistent sessions via the --session=SESSION_NAME_OR_PATH option. In a session, custom HTTP headers (except for the ones starting with Content- or If-), authentication, and cookies (manually specified or sent by the server) persist between requests to the same host.

# Create a new session:
$ http --session=./session.json API-Token:123
# Inspect / edit the generated session file:
$ cat session.json
# Re-use the existing session — the API-Token header will be set:
$ http --session=./session.json

All session data, including credentials, cookie data, and custom headers are stored in plain text. That means session files can also be created and edited manually in a text editor—they are regular JSON. It also means that they can be read by anyone who has access to the session file.

24.1   Named sessions

You can create one or more named session per host. For example, this is how you can create a new session named user1 for

$ http --session=user1 -a user1:password X-Foo:Bar

From now on, you can refer to the session by its name (user1). When you choose to use the session again, any previously specified authentication or HTTP headers will automatically be set:

$ http --session=user1

To create or reuse a different session, simple specify a different name:

$ http --session=user2 -a user2:password X-Bar:Foo

Named sessions’s data is stored in JSON files inside the sessions subdirectory of the config directory, typically: ~/.config/httpie/sessions/<host>/<name>.json (%APPDATA%\httpie\sessions\<host>\<name>.json on Windows).

If you have executed the above commands on a unix machine, you should be able list the generated sessions files using:

$ ls -l ~/.config/httpie/sessions/

24.2   Anonymous sessions

Instead of a name, you can also directly specify a path to a session file. This allows for sessions to be re-used across multiple hosts:

# Create a session:
$ http --session=/tmp/session.json
# Use the session to make a request to another host:
$ http --session=/tmp/session.json
# You can also refer to a previously created named session:
$ http --session=~/.config/httpie/sessions/

When creating anonymous sessions, please remember to always include at least one /, even if the session files is located in the current directory (i.e., --session=./session.json instead of just --session=session.json), otherwise HTTPie assumes a named session instead.

24.3   Readonly session

To use an existing session file without updating it from the request/response exchange after it has been created, specify the session name via --session-read-only=SESSION_NAME_OR_PATH instead.

# If the session file doesn’t exist, then it is created:
$ http --session-read-only=./ro-session.json Custom-Header:orig-value
# But it is not updated:
$ http --session-read-only=./ro-session.json Custom-Header:new-value

24.4   Cookie Storage Behaviour

TL;DR: Cookie storage priority: Server response > Command line request > Session file

To set a cookie within a Session there are three options:

  1. Get a Set-Cookie header in a response from a server
$ http --session=./session.json
  1. Set the cookie name and value through the command line as seen in cookies
$ http --session=./session.json Cookie:foo=bar
  1. Manually set cookie parameters in the json file of the session
    "__meta__": {
    "about": "HTTPie session file",
    "help": "",
    "httpie": "2.2.0-dev"
    "auth": {
        "password": null,
        "type": null,
        "username": null
    "cookies": {
        "foo": {
            "expires": null,
            "path": "/",
            "secure": false,
            "value": "bar"

Cookies will be set in the session file with the priority specified above. For example, a cookie set through the command line will overwrite a cookie of the same name stored in the session file. If the server returns a Set-Cookie header with a cookie of the same name, the returned cookie will overwrite the preexisting cookie.

Expired cookies are never stored. If a cookie in a session file expires, it will be removed before sending a new request. If the server expires an existing cookie, it will also be removed from the session file.

25   Config

HTTPie uses a simple config.json file. The file doesn’t exist by default but you can create it manually.

25.1   Config file directory

To see the exact location for your installation, run http --debug and look for config_dir in the output.

The default location of the configuration file on most platforms is $XDG_CONFIG_HOME/httpie/config.json (defaulting to ~/.config/httpie/config.json).

For backwards compatibility, if the directory ~/.httpie exists, the configuration file there will be used instead.

On Windows, the config file is located at %APPDATA%\httpie\config.json.

The config directory can be changed by setting the $HTTPIE_CONFIG_DIR environment variable:

$ export HTTPIE_CONFIG_DIR=/tmp/httpie
$ http

25.2   Configurable options

Currently HTTPie offers a single configurable option:

25.2.1   default_options

An Array (by default empty) of default options that should be applied to every invocation of HTTPie.

For instance, you can use this config option to change your default color theme:

$ cat ~/.config/httpie/config.json
    "default_options": [

Even though it is technically possible to include there any of HTTPie’s options, it is not recommended to modify the default behaviour in a way that would break your compatibility with the wider world as that can generate a lot of confusion.

25.3   Un-setting previously specified options

Default options from the config file, or specified any other way, can be unset for a particular invocation via --no-OPTION arguments passed on the command line (e.g., --no-style or --no-session).

26   Scripting

When using HTTPie from shell scripts, it can be handy to set the --check-status flag. It instructs HTTPie to exit with an error if the HTTP status is one of 3xx, 4xx, or 5xx. The exit status will be 3 (unless --follow is set), 4, or 5, respectively.


if http --check-status --ignore-stdin --timeout=2.5 HEAD &> /dev/null; then
    echo 'OK!'
    case $? in
        2) echo 'Request timed out!' ;;
        3) echo 'Unexpected HTTP 3xx Redirection!' ;;
        4) echo 'HTTP 4xx Client Error!' ;;
        5) echo 'HTTP 5xx Server Error!' ;;
        6) echo 'Exceeded --max-redirects=<n> redirects!' ;;
        *) echo 'Other Error!' ;;

26.1   Best practices

The default behaviour of automatically reading stdin is typically not desirable during non-interactive invocations. You most likely want to use the --ignore-stdin option to disable it.

It is a common gotcha that without this option HTTPie seemingly hangs. What happens is that when HTTPie is invoked for example from a cron job, stdin is not connected to a terminal. Therefore, rules for redirected input apply, i.e., HTTPie starts to read it expecting that the request body will be passed through. And since there’s no data nor EOF, it will be stuck. So unless you’re piping some data to HTTPie, this flag should be used in scripts.

Also, it might be good to set a connection --timeout limit to prevent your program from hanging if the server never responds.

27   Meta

27.1   Interface design

The syntax of the command arguments closely corresponds to the actual HTTP requests sent over the wire. It has the advantage that it’s easy to remember and read. It is often possible to translate an HTTP request to an HTTPie argument list just by inlining the request elements. For example, compare this HTTP request:

POST /post HTTP/1.1
X-API-Key: 123
User-Agent: Bacon/1.0
Content-Type: application/x-www-form-urlencoded


with the HTTPie command that sends it:

$ http -f POST \
  X-API-Key:123 \
  User-Agent:Bacon/1.0 \
  name=value \

Notice that both the order of elements and the syntax is very similar, and that only a small portion of the command is used to control HTTPie and doesn’t directly correspond to any part of the request (here it’s only -f asking HTTPie to send a form request).

The two modes, --pretty=all (default for terminal) and --pretty=none (default for redirected output), allow for both user-friendly interactive use and usage from scripts, where HTTPie serves as a generic HTTP client.

As HTTPie is still under heavy development, the existing command line syntax and some of the --OPTIONS may change slightly before HTTPie reaches its final version 1.0. All changes are recorded in the change log.

27.2   Community and Support

HTTPie has the following community channels:

27.3   Related projects

27.3.1   Dependencies

Under the hood, HTTPie uses these two amazing libraries:

  • Requests — Python HTTP library for humans
  • Pygments — Python syntax highlighter

27.3.2   HTTPie friends

HTTPie plays exceptionally well with the following tools:

  • http-prompt — interactive shell for HTTPie featuring autocomplete and command syntax highlighting
  • jq — CLI JSON processor that works great in conjunction with HTTPie

Helpers to convert from other client tools:

  • CurliPie help convert cURL command line to HTTPie command line.

27.3.3   Alternatives

  • httpcat — a lower-level sister utility of HTTPie for constructing raw HTTP requests on the command line.
  • curl — a "Swiss knife" command line tool and an exceptional library for transferring data with URLs.

27.4   Contributing


27.5   Change log


27.6   Artwork

27.7   Licence

BSD-3-Clause: LICENSE.

27.8   Authors

Jakub Roztocil (@jakubroztocil) created HTTPie and these fine people have contributed.

  • Issue for Testing

    Issue for Testing

    Test httpie advanced usage by posting a comment on this issue:

    http -a <username> body='Your Comment'
    opened by jakubroztocil 448
  • Option to allow pretty print without alpha sorting

    Option to allow pretty print without alpha sorting

    Right now, the options are colors, format, and all, but often the order of the json returned is intentional and for clarify. It would be nice to be able to pretty print the json without having it's keys sorted :)

    Awesome tool, and thanks very much for everything!

    opened by patcon 36
  • httpie changing the json fields order in the output

    httpie changing the json fields order in the output

    Wondering how can I force httpie to not change the json fields order?

    curl -i http://localhost:8080/v1/notes/569766aed4c661fba8d85a12
      "id": "569766aed4c661fba8d85a12",
      "content": "hi"

    with httpie

    http get :8080/v1/notes/569766aed4c661fba8d85a12 
      "content": "hi",
      "id": "569766aed4c661fba8d85a12"

    I prefer the id field to be always the first. Any thoughts?

    opened by altfatterz 27
  • Multiple test failures in tox py34

    Multiple test failures in tox py34

    Multiple test failures in

    When I run:

    tox -e py34 -- tests/

    I get 1, 2, or 3 test failures out of the 7 total tests in that module.

    tests/ PASSED
    tests/ FAILED
    tests/ FAILED
    tests/ PASSED
    tests/ PASSED
    tests/ FAILED
    tests/ PASSED

    More info:

    TestSessionFlow.test_session_update fails with:

    requests.exceptions.ConnectionError: (
    'Connection aborted.', ConnectionResetError(54, 'Connection reset by peer'))

    pdb for above error shows:

    > /Users/marca/dev/git-repos/httpie/.tox/py34/lib/python3.4/site-packages/requests/
    -> raise ConnectionError(err, request=request)
    (Pdb) up
    > /Users/marca/dev/git-repos/httpie/.tox/py34/lib/python3.4/site-packages/requests/
    -> r = adapter.send(request, **kwargs)
    (Pdb) request.method
    (Pdb) request.url
    (Pdb) request.headers
    {'Accept-Encoding': 'gzip, deflate', 'Hello': b'World2', 'Cookie': 'hello=world; hello=world2', 'Connection': 'keep-alive', 'Authorization': b'Basic dXNlcm5hbWU6cGFzc3dvcmQy', 'Accept': '*/*', 'User-Agent': b'HTTPie/0.9.0-dev'}
    (Pdb) kwargs
    {'timeout': 30, 'cert': None, 'proxies': {}, 'stream': True, 'verify': True}

    TestSessionFlow.test_session_read_only fails with

    requests.exceptions.ConnectionError: ('Connection aborted.', BadStatusLine("''",))

    pdb for above error shows:

    > /Users/marca/dev/git-repos/httpie/.tox/py34/lib/python3.4/site-packages/requests/
    -> raise ConnectionError(err, request=request)
    (Pdb) up
    > /Users/marca/dev/git-repos/httpie/.tox/py34/lib/python3.4/site-packages/requests/
    -> r = adapter.send(request, **kwargs)
    (Pdb) request.method
    (Pdb) request.url
    (Pdb) request.headers
    {'User-Agent': b'HTTPie/0.9.0-dev', 'Hello': b'World2', 'Accept-Encoding': 'gzip, deflate', 'Cookie': 'hello=world; hello=world2', 'Connection': 'keep-alive', 'Authorization': b'Basic dXNlcm5hbWU6cGFzc3dvcmQy', 'Accept': '*/*'}
    (Pdb) kwargs
    {'cert': None, 'proxies': {}, 'verify': True, 'timeout': 30, 'stream': True}

    TestSession.test_session_unicode fails with:

    Traceback (most recent call last):
      File ".../httpie/tests/", line 148, in test_session_unicode
        assert (r2.json['headers']['Authorization']
    KeyError: 'Authorization'

    Pertaining to this last error, there is a comment in the test saying:

    147             # FIXME: Authorization *sometimes* is not present on Python3
    (Pdb) pprint.pprint(r2.json)
    {'args': {},
     'headers': {'Content-Length': '',
                 'Host': '',
                 'Test': '[one line of UTF8-encoded unicode text] Ï\x87Ï\x81Ï'},
     'origin': '',
     'url': ''}

    In py33 I also see 1 to 2 test failures -- I have not yet observed TestSession.test_session_unicode failing on py33.

    Most of the time, all these tests pass on py27, though I am seeing test_session_read_only fail occasionally with:

    ____________________________________________________________________ TestSessionFlow.test_session_read_only ____________________________________________________________________
    Traceback (most recent call last):
      File "/Users/marca/dev/git-repos/httpie/tests/", line 82, in test_session_read_only
      File "/Users/marca/dev/git-repos/httpie/tests/", line 48, in start_session
      File "/Users/marca/dev/git-repos/httpie/tests/", line 136, in http
        exit_status = main(args=args, **kwargs)
      File "/Users/marca/dev/git-repos/httpie/.tox/py27/lib/python2.7/site-packages/httpie/", line 112, in main
        response = get_response(args,
      File "/Users/marca/dev/git-repos/httpie/.tox/py27/lib/python2.7/site-packages/httpie/", line 31, in get_response
      File "/Users/marca/dev/git-repos/httpie/.tox/py27/lib/python2.7/site-packages/httpie/", line 65, in get_response
        response = requests_session.request(**requests_kwargs)
      File "/Users/marca/dev/git-repos/httpie/.tox/py27/lib/python2.7/site-packages/requests/", line 457, in request
        resp = self.send(prep, **send_kwargs)
      File "/Users/marca/dev/git-repos/httpie/.tox/py27/lib/python2.7/site-packages/requests/", line 595, in send
        history = [resp for resp in gen] if allow_redirects else []
      File "/Users/marca/dev/git-repos/httpie/.tox/py27/lib/python2.7/site-packages/requests/", line 189, in resolve_redirects
      File "/Users/marca/dev/git-repos/httpie/.tox/py27/lib/python2.7/site-packages/requests/", line 569, in send
        r = adapter.send(request, **kwargs)
      File "/Users/marca/dev/git-repos/httpie/.tox/py27/lib/python2.7/site-packages/requests/", line 407, in send
        raise ConnectionError(err, request=request)
    ConnectionError: ('Connection aborted.', error(54, 'Connection reset by peer'))
    opened by msabramo 26
  • Add support for unix domain sockets

    Add support for unix domain sockets

    To issue HTTP requests to a UNIX domain socket:

    • Use new "http+unix://" scheme in URL.

    • Use urlencoded socket path as the hostname part of the URL. e.g.: for a socket at /tmp/profilesvc.sock, you could do:

      http http+unix://%2Ftmp%2Fprofilesvc.sock/status/pid

    This uses

    Fixes: GH-209 (


    screen shot 2014-11-24 at 6 35 24 pm

    Cc: @shin-, @jakubroztocil, @monsanto, @np, @nuxlli, @matrixise, @remmelt

    opened by msabramo 26
  • requests.exceptions.SSLError: [Errno 8] _ssl.c:507: EOF occurred in violation of protocol

    requests.exceptions.SSLError: [Errno 8] _ssl.c:507: EOF occurred in violation of protocol

    HTTPie 1.0.0-dev
    HTTPie data: /Users/kaji/.httpie
    Requests 2.5.3
    Pygments 2.0.2
    Python 2.7.6 (default, Sep  9 2014, 15:04:36)
    [GCC 4.2.1 Compatible Apple LLVM 6.0 (clang-600.0.39)] darwin
    Not every SSL website shows though. So, it is tricky. From browser , it is working fine.
    >>> requests.request({'allow_redirects': False,
     'auth': None,
     'cert': None,
     'data': OrderedDict(),
     'files': DataDict(),
     'headers': {'User-Agent': 'HTTPie/1.0.0-dev'},
     'method': 'get',
     'params': ParamsDict(),
     'proxies': {},
     'stream': True,
     'timeout': 30,
     'url': u'',
     'verify': True})
    Traceback (most recent call last):
      File "/usr/local/bin/http", line 9, in <module>
        load_entry_point('httpie==1.0.0-dev', 'console_scripts', 'http')()
      File "/Library/Python/2.7/site-packages/httpie/", line 112, in main
        response = get_response(args,
      File "/Library/Python/2.7/site-packages/httpie/", line 41, in get_response
        response = requests_session.request(**kwargs)
      File "/Library/Python/2.7/site-packages/requests/", line 461, in request
        resp = self.send(prep, **send_kwargs)
      File "/Library/Python/2.7/site-packages/requests/", line 573, in send
        r = adapter.send(request, **kwargs)
      File "/Library/Python/2.7/site-packages/requests/", line 431, in send
        raise SSLError(e, request=request)
    requests.exceptions.SSLError: [Errno 8] _ssl.c:507: EOF occurred in violation of protocol
    opened by kaji-bikash 24
  • Syntax for nested JSON

    Syntax for nested JSON

    The simple examples work, but what about nested data? In curl I do something like this:

    '"credentials": { "username": "me", "key": "my-key"} }'

    How can I do this with httpie?

    enhancement planned needs product design 
    opened by sym3tri 23
  • Request to add `-d, --data` option for raw body like curl

    Request to add `-d, --data` option for raw body like curl

    The request is simple, just to add an option to pass raw data like curl does:

    http :/api/user -d 'MyRawData...'

    I know that in mostly cases if you are sending JSON or form data, it can be achieved with the "request items", like:

    http :/api/hey say=Hello to=me …

    And it will converted to the proper format depending of the content type, that is awesome! And if you have something that is not a JSON or form data to send, you can do something like:

    echo 'MyRawData...' | http :/api/hey

    But this is impractical, the main idea of HTTPie is cURL-like tool for humans , and this case is far of that principle, in fact, curl is more practical than HTTPie for the previous example. Adding more than one command and pipe them with ugly characters like | < just because a simple option is missing doesn't sound human-friendly.

    What's wrong with add the -d option to http?

    opened by mrsarm 22
  • httpie output has lots of additional characters on windows

    httpie output has lots of additional characters on windows

    Running http GET on windows results in a load of extra characters being printed out:

    HTTP/1.1 ←[39;49;00m←[34m302←[39;49;00m←[33m Found←[39;49;00m
    Date:←[39;49;00m←[33m Mon, 19 Mar 2012 15:13:17 GMT←[39;49;00m
    Server:←[39;49;00m←[33m Apache←[39;49;00m
    X-Awesome:←[39;49;00m←[33m Thanks for trying HTTPie :)←[39;49;00m
    Cache-Control:←[39;49;00m←[33m max-age=1800←[39;49;00m
    Expires:←[39;49;00m←[33m Mon, 19 Mar 2012 15:43:17 GMT←[39;49;00m
    Content-Length:←[39;49;00m←[33m 214←[39;49;00m
    Content-Type:←[39;49;00m←[33m text/html; charset=iso-8859-1←[39;49;00m
    ←[36m<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">←[39;49;00m
    ←[34;01m<title←[39;49;00m←[34;01m>←[39;49;00m302 Found←[39;49;00m←[34;01m</title>←[39;49;00m
    ←[34;01m<p←[39;49;00m←[34;01m>←[39;49;00mThe document has moved ←[39;49;00m←[34;01m<a←[39;49;00m ←[39;49;00m←[36mhref=←[39;49;00m←[33m""←[39;49;00m←[34;01m>←[39;49;00mhere←[39;49;00m←[34;01m</a>←[39;49;00m.←[39;49;00m←[34;01m</p>←[39;49;00m

    I'm guessing that these are escape codes that provide the colored output on other operating systems. Running http -u GET results in correct (though monochrome) output.

    It'd be nice to get cross platform colored output like provided by clint.

    bug windows 
    opened by obmarg 20
  • Brew installed version doesn't work with plugins

    Brew installed version doesn't work with plugins

    Brew is listed as the recommended way of installing httpie on macOS. However, it doesn't work with auth plugins.

    For example, if you pip3 install requests-hawk and then run http --help hawk will not show as an auth type. If you pip3 install httpie-oauth it will install httpie via pip as a dependency and overwrite the brew installed link in /usr/local/bin/http and now all the plugins will show because it isn't using the brew installed version.

    I suggest changing the documentation to read pip3 install httpie as the recommended method of installing on macOS.

    bug docs 
    opened by rshurts 19
  • Not working on OS X Mavericks

    Not working on OS X Mavericks

    When I tried to run a command on OS X Mavericks, I get the following error:

    batuhanicoz at batuhanicoz-mbp2 in ~
    ○ http GET
    Traceback (most recent call last):
      File "/usr/local/bin/http", line 5, in <module>
        from pkg_resources import load_entry_point
      File "/System/Library/Frameworks/Python.framework/Versions/2.7/Extras/lib/python/", line 2603, in <module>
      File "/System/Library/Frameworks/Python.framework/Versions/2.7/Extras/lib/python/", line 666, in require
        needed = self.resolve(parse_requirements(requirements))
      File "/System/Library/Frameworks/Python.framework/Versions/2.7/Extras/lib/python/", line 565, in resolve
        raise DistributionNotFound(req)  # XXX put more info here
    pkg_resources.DistributionNotFound: httpie==0.6.0
    opened by batuhan 19
  • Bump mislav/bump-homebrew-formula-action from 1 to 2

    Bump mislav/bump-homebrew-formula-action from 1 to 2

    Bumps mislav/bump-homebrew-formula-action from 1 to 2.

    Release notes

    Sourced from mislav/bump-homebrew-formula-action's releases.

    bump-homebrew-formula 2.0

    What's Changed

    New Contributors

    bump-homebrew-formula 1.16

    bump-homebrew-formula 1.14

    • Ignore HTTP 409 error when fast-forwading the main branch of homebrew-tap fork

    bump-homebrew-formula 1.13

    • Add create-pullrequest input to control whether or not a PR is submitted to homebrew-tap
    • Add download-sha256 input to define the SHA256 checksum of the archive at download-url
    • Fix creating a new branch in the forked repo failing with HTTP 404

    bump-homebrew-formula 1.12

    • Fix Actions CJS loader halting on foo?.bar JS syntax

    bump-homebrew-formula 1.11

    • New optional formula-path input accepts the filename of the formula file to edit (default Formula/<formula-name>.rb).
    • Remove revision N lines when bumping Homebrew formulae.

    bump-homebrew-formula 1.10

    bump-homebrew-formula 1.9

    • Fix following multiple HTTP redirects while calculating checksum for download-url

    bump-homebrew-formula 1.8

    • Enable JavaScript source maps for better failure debugging

    bump-homebrew-formula 1.7

    • Allow download-url as input parameter

    • Add support for git-based download-url

    bump-homebrew-formula 1.6

    • Control the git commit message template being used for updating the formula file via the commit-message action input

    bump-homebrew-formula 1.5

    • Support detection version from download URLs

    ... (truncated)


    Dependabot compatibility score

    Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

    Dependabot commands and options

    You can trigger Dependabot actions by commenting on this PR:

    • @dependabot rebase will rebase this PR
    • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
    • @dependabot merge will merge this PR after your CI passes on it
    • @dependabot squash and merge will squash and merge this PR after your CI passes on it
    • @dependabot cancel merge will cancel a previously requested merge and block automerging
    • @dependabot reopen will reopen this PR if it is closed
    • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
    • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
    • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
    • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
    opened by dependabot[bot] 0
  • Nested JSON with property name containing colon interpreted as header declaration

    Nested JSON with property name containing colon interpreted as header declaration

    The Nested JSON CLI syntax allows me to construct a request body without having to type out the raw JSON (loving it), but it seems to collide with how arguments can be interpreted as headers. I'm expecting http POST foo[bar:baz]=foobar --print=HB and http POST foo:='{"bar:baz": "foobar"}' --print=HB to produce identical results, but when using the nested JSON syntax, httpie interprets my argument as the foo[bar header (which is an invalid HTTP header field name) having the baz]=foobar value.

    $ http POST foo[bar:baz]=foobar --print=HB
    POST /hello HTTP/1.1
    Accept: */*
    Accept-Encoding: gzip, deflate
    Connection: keep-alive
    Content-Length: 0
    User-Agent: HTTPie/3.2.1
    foo[bar: baz]=foobar

    should produce the same result as

    $ http POST foo:='{"bar:baz": "foobar"}' --print=HB
    POST /hello HTTP/1.1
    Accept: application/json, */*;q=0.5
    Accept-Encoding: gzip, deflate
    Connection: keep-alive
    Content-Length: 30
    Content-Type: application/json
    User-Agent: HTTPie/3.2.1
        "foo": {
            "bar:baz": "foobar"

    I think it's reasonable that nested JSON object specification on the CLI should take precedence over the intent to specify an http header, since the latter would be illegal and not accepted by many HTTP servers. For reference, xh also contains this problem, but doesn't attempt to make the request:

    $ xh POST foo[bar:baz]=foobar --print=HB
    xh: error: invalid HTTP header name
    bug new 
    opened by ingemaradahl 5
  • Interview partners for research about communication in GitHub projects wanted

    Interview partners for research about communication in GitHub projects wanted

    Hi. My name is Verena Ebert, and I am a PhD student at the University of Stuttgart in Germany.
    A few months ago, I have examined 90 GitHub projects to see what communication channels they use and how they write about them in the written documents, for example README or wiki. If you are interested in the previous results, you can find them here: Your project was one of these 90 projects and, therefore, I am interested in further details about your communication setup.

    To gather more data about your communication setup, I kindly ask one of the maintainers to do an interview with me. The interview will be about 30-35 minutes long and via Skype, WebEx or any other provider you prefer. The interviews should be done in November 2022, if possible.

    In this interview, I would like to ask some questions about the reasons behind the channels, to understand the thoughts of the maintainers in addition to the written information.

    The long goal of my PhD is to understand how communication works in GitHub projects and how a good set of communication channels and information for other maintainers and developers looks like. One possible outcome is a with instructions and tips about which channels could be useful and how these channels should be introduced to other projects participants. Of course, if you are interested, I will keep you up to date about any further results in my research.

    If you are interested in doing an interview, please respond here or contact me via email ([email protected]). We will then make an appointment for the interview at a time and date that suits you.

    If you agree, I would like to record the interview and transcribe the spoken texts into anonymized written texts. In this case, I will send you the transcript for corrections afterwards. Only if you agree, the transcripts or parts of it would be part of a publication.

    opened by verenya 0
  • Authorization header not printed when using digest auth

    Authorization header not printed when using digest auth

    http -v -A digest -a username:password doesn't print the Authorization request header

    I guess this is challenging because the header is populated in the requests library

    > http -v -A digest -a username:password --debug
    HTTPie 3.2.1
    Requests 2.26.0
    Pygments 2.7.1
    Python 3.9.2 (default, Feb 28 2021, 17:03:44) 
    [GCC 10.2.1 20210110]
    Linux 5.10.142-19739-g5899aa8f604c
    <Environment {'apply_warnings_filter': <function Environment.apply_warnings_filter at 0x7aa7d104e700>,
     'args': Namespace(),
     'as_silent': <function Environment.as_silent at 0x7aa7d104e5e0>,
     'colors': 256,
     'config': {'default_options': []},
     'config_dir': PosixPath('/home/matt/.config/httpie'),
     'devnull': <property object at 0x7aa7d10f90e0>,
     'is_windows': False,
     'log_error': <function Environment.log_error at 0x7aa7d104e670>,
     'program_name': 'http',
     'quiet': 0,
     'rich_console': <functools.cached_property object at 0x7aa7d1118d00>,
     'rich_error_console': <functools.cached_property object at 0x7aa7d10b1ee0>,
     'show_displays': True,
     'stderr': <_io.TextIOWrapper name='<stderr>' mode='w' encoding='utf-8'>,
     'stderr_isatty': True,
     'stdin': <_io.TextIOWrapper name='<stdin>' mode='r' encoding='utf-8'>,
     'stdin_encoding': 'utf-8',
     'stdin_isatty': True,
     'stdout': <_io.TextIOWrapper name='<stdout>' mode='w' encoding='utf-8'>,
     'stdout_encoding': 'utf-8',
     'stdout_isatty': True}>
    <PluginManager {'adapters': [],
     'auth': [<class 'httpie.plugins.builtin.BasicAuthPlugin'>,
              <class 'httpie.plugins.builtin.DigestAuthPlugin'>,
              <class 'httpie.plugins.builtin.BearerAuthPlugin'>],
     'converters': [],
     'formatters': [<class 'httpie.output.formatters.headers.HeadersFormatter'>,
                    <class 'httpie.output.formatters.json.JSONFormatter'>,
                    <class 'httpie.output.formatters.xml.XMLFormatter'>,
                    <class 'httpie.output.formatters.colors.ColorFormatter'>]}>
    >>> requests.request(**{'auth': <requests.auth.HTTPDigestAuth object at 0x7aa7d0ddce80>,
     'data': RequestJSONDataDict(),
     'headers': <HTTPHeadersDict('User-Agent': b'HTTPie/3.2.1')>,
     'method': 'get',
     'params': <generator object MultiValueOrderedDict.items at 0x7aa7d0c63ac0>,
     'url': ''})
    GET /digest-auth/auth/username/password HTTP/1.1
    Accept: */*
    Accept-Encoding: gzip, deflate
    Connection: keep-alive
    User-Agent: HTTPie/3.2.1
    HTTP/1.1 200 OK
    Access-Control-Allow-Credentials: true
    Access-Control-Allow-Origin: *
    CF-Cache-Status: DYNAMIC
    CF-RAY: 764f8c0d5d7e72c7-LHR
    Connection: keep-alive
    Content-Encoding: gzip
    Content-Type: application/json
    Date: Fri, 04 Nov 2022 18:52:29 GMT
    NEL: {"success_fraction":0,"report_to":"cf-nel","max_age":604800}
    Report-To: {"endpoints":[{"url":"https:\/\/\/report\/v3?s=ZopT9m6iwhzwDZHMAedQf0kZ4yELEqrElPOpkJwwm7w4BqJi9qVHrFlwBmKpWJT8%2FZxbLcdm%2B2HN2h2Cz%2FO0eS6JPqGeqN9wOum0%2F7wvvFv6f465Gu%2BEUNVE"}],"group":"cf-nel","max_age":604800}
    Server: cloudflare
    Set-Cookie: fake=fake_value; Path=/
    Set-Cookie: stale_after=never; Path=/
    Transfer-Encoding: chunked
    alt-svc: h3=":443"; ma=86400, h3-29=":443"; ma=86400
        "authenticated": true,
        "user": "username"
    bug new 
    opened by hickford 1
  • Digest authentication with qop=auth-int fails

    Digest authentication with qop=auth-int fails "TypeError: expected string or bytes-like object"

    > http -A digest -a username:password
    http: error: TypeError: expected string or bytes-like object

    See for more about qop

    Debug output

    Please re-run the command with --debug, then copy the entire command & output and paste both below:

    > http --debug -A digest -a username:password
    HTTPie 3.2.1
    Requests 2.26.0
    Pygments 2.7.1
    Python 3.9.2 (default, Feb 28 2021, 17:03:44) 
    [GCC 10.2.1 20210110]
    Linux 5.10.142-19739-g5899aa8f604c
    <Environment {'apply_warnings_filter': <function Environment.apply_warnings_filter at 0x7a2958066700>,
     'args': Namespace(),
     'as_silent': <function Environment.as_silent at 0x7a29580665e0>,
     'colors': 256,
     'config': {'default_options': []},
     'config_dir': PosixPath('/home/matt/.config/httpie'),
     'devnull': <property object at 0x7a29580d0b80>,
     'is_windows': False,
     'log_error': <function Environment.log_error at 0x7a2958066670>,
     'program_name': 'http',
     'quiet': 0,
     'rich_console': <functools.cached_property object at 0x7a2958130d30>,
     'rich_error_console': <functools.cached_property object at 0x7a29580c7f10>,
     'show_displays': True,
     'stderr': <_io.TextIOWrapper name='<stderr>' mode='w' encoding='utf-8'>,
     'stderr_isatty': True,
     'stdin': <_io.TextIOWrapper name='<stdin>' mode='r' encoding='utf-8'>,
     'stdin_encoding': 'utf-8',
     'stdin_isatty': True,
     'stdout': <_io.TextIOWrapper name='<stdout>' mode='w' encoding='utf-8'>,
     'stdout_encoding': 'utf-8',
     'stdout_isatty': True}>
    <PluginManager {'adapters': [],
     'auth': [<class 'httpie.plugins.builtin.BasicAuthPlugin'>,
              <class 'httpie.plugins.builtin.DigestAuthPlugin'>,
              <class 'httpie.plugins.builtin.BearerAuthPlugin'>],
     'converters': [],
     'formatters': [<class 'httpie.output.formatters.headers.HeadersFormatter'>,
                    <class 'httpie.output.formatters.json.JSONFormatter'>,
                    <class 'httpie.output.formatters.xml.XMLFormatter'>,
                    <class 'httpie.output.formatters.colors.ColorFormatter'>]}>
    >>> requests.request(**{'auth': <requests.auth.HTTPDigestAuth object at 0x7a2957e9e190>,
     'data': RequestJSONDataDict(),
     'headers': <HTTPHeadersDict('User-Agent': b'HTTPie/3.2.1')>,
     'method': 'get',
     'params': <generator object MultiValueOrderedDict.items at 0x7a2957c7bac0>,
     'url': ''})
    http: error: TypeError: expected string or bytes-like object
    Traceback (most recent call last):
      File "/home/matt/.local/bin/http", line 8, in <module>
      File "/home/matt/.local/lib/python3.9/site-packages/httpie/", line 9, in main
        exit_status = main()
      File "/home/matt/.local/lib/python3.9/site-packages/httpie/", line 162, in main
        return raw_main(
      File "/home/matt/.local/lib/python3.9/site-packages/httpie/", line 140, in raw_main
      File "/home/matt/.local/lib/python3.9/site-packages/httpie/", line 100, in raw_main
        exit_status = main_program(
      File "/home/matt/.local/lib/python3.9/site-packages/httpie/", line 213, in program
        for message in messages:
      File "/home/matt/.local/lib/python3.9/site-packages/httpie/", line 111, in collect_messages
        response = requests_session.send(
      File "/home/matt/.local/lib/python3.9/site-packages/requests/", line 662, in send
        r = dispatch_hook('response', hooks, r, **kwargs)
      File "/home/matt/.local/lib/python3.9/site-packages/requests/", line 31, in dispatch_hook
        _hook_data = hook(hook_data, **kwargs)
      File "/home/matt/.local/lib/python3.9/site-packages/requests/", line 269, in handle_401
        _r = r.connection.send(prep, **kwargs)
      File "/home/matt/.local/lib/python3.9/site-packages/requests/", line 439, in send
        resp = conn.urlopen(
      File "/home/matt/.local/lib/python3.9/site-packages/urllib3/", line 699, in urlopen
        httplib_response = self._make_request(
      File "/home/matt/.local/lib/python3.9/site-packages/urllib3/", line 394, in _make_request
        conn.request(method, url, **httplib_request_kw)
      File "/home/matt/.local/lib/python3.9/site-packages/urllib3/", line 239, in request
        super(HTTPConnection, self).request(method, url, body=body, headers=headers)
      File "/usr/lib/python3.9/http/", line 1255, in request
        self._send_request(method, url, body, headers, encode_chunked)
      File "/usr/lib/python3.9/http/", line 1296, in _send_request
        self.putheader(hdr, value)
      File "/home/matt/.local/lib/python3.9/site-packages/urllib3/", line 224, in putheader
        _HTTPConnection.putheader(self, header, *values)
      File "/usr/lib/python3.9/http/", line 1232, in putheader
        if _is_illegal_header_value(values[i]):
    TypeError: expected string or bytes-like object```
    bug new 
    opened by hickford 0
  • 3.2.1(May 6, 2022)

    • Improved support for determining auto-streaming when the Content-Type header includes encoding information. (#1383)
    • Fixed the display of the crash happening in the secondary process for update checks. (#1388)

    → Join our Discord community: → Install HTTPie: → Learn more:

    Source code(tar.gz)
    Source code(zip)
    http(9.44 MB)
    httpie-3.2.1.deb(26.90 MB)
  • 3.2.0(May 5, 2022)

    • Added a warning for notifying the user about the new updates. (#1336)
    • Added support for single binary executables. (#1330)
    • Added support for man pages (and auto generation of them from the parser declaration). (#1317)
    • Added http --manual for man pages & regular manual with pager. (#1343)
    • Added support for session persistence of repeated headers with the same name. (#1335)
    • Added support for sending Secure cookies to the localhost (and .local suffixed domains). (#1308)
    • Improved UI for the progress bars. (#1324)
    • Fixed redundant creation of Content-Length header on OPTIONS requests. (#1310)
    • Fixed blocking of warning thread on some use cases. (#1349)
    • Changed httpie plugins to the new httpie cli namespace as httpie cli plugins (httpie plugins continues to work as a hidden alias). (#1320)
    • Soft deprecated the --history-print. (#1380)

    → Join our Discord community: → Install HTTPie: → Learn more:

    Source code(tar.gz)
    Source code(zip)
    http(9.44 MB)
    httpie-3.2.0.deb(26.90 MB)
  • 3.1.0(Mar 7, 2022)

    • SECURITY Fixed the vulnerability that caused exposure of cookies on redirects to third party hosts. (#1312)
    • Fixed escaping of integer indexes with multiple backslashes in the nested JSON builder. (#1285)
    • Fixed displaying of status code without a status message on non-auto themes. (#1300)
    • Fixed redundant issuance of stdin detection warnings on some rare cases due to underlying implementation. (#1303)
    • Fixed double --quiet so that it will now suppress all python level warnings. (#1271)
    • Added support for specifying certificate private key passphrases through --cert-key-pass and prompts. (#946)
    • Added httpie cli export-args command for exposing the parser specification for the http/https commands. (#1293)
    • Improved regulation of top-level arrays. (#1292)
    • Improved UI layout for standalone invocations. (#1296)

    → Join our Discord community: → Install HTTPie: → Learn more:

    Source code(tar.gz)
    Source code(zip)
    http(9.19 MB)
    httpie_3.1.0_amd64.deb(26.35 MB)
  • 3.0.2(Jan 24, 2022)

  • 3.0.1(Jan 23, 2022)

  • 3.0.0(Jan 21, 2022)

    What’s new in HTTPie for Terminal 3.0 →

    🌲️ Nested JSON 🔌 Plugin manager ⏱️ Response metadata 🚀 Speed-ups 🎨 Improved UI/UX ✨ Other minor features 🪲 Bug fixes

    • Dropped support for Python 3.6. (#1177)
    • Improved startup time by 40%. (#1211)
    • Added support for nested JSON syntax. (#1169)
    • Added httpie plugins interface for plugin management. (#566)
    • Added support for Bearer authentication via --auth-type=bearer (#1215).
    • Added support for quick conversions of pasted URLs into HTTPie calls by adding a space after the protocol name ($ https ://pie.dev (#1195)
    • Added support for sending multiple HTTP header lines with the same name. (#130)
    • Added support for receiving multiple HTTP headers lines with the same name. (#1207)
    • Added support for basic JSON types on --form/--multipart when using JSON only operators (:=/:[email protected]). (#1212)
    • Added support for automatically enabling --stream when Content-Type is text/event-stream. (#376)
    • Added support for displaying the total elapsed time through --meta/-vv or --print=m. (#243)
    • Added new pie-dark/pie-light (and pie) styles that match with HTTPie for Web and Desktop. (#1237)
    • Added support for better error handling on DNS failures. (#1248)
    • Added support for storing prompted passwords in the local sessions. (#1098)
    • Added warnings about the --ignore-stdin, when there is no incoming data from stdin. (#1255)
    • Fixed crashing due to broken plugins. (#1204)
    • Fixed auto addition of XML declaration to every formatted XML response. (#1156)
    • Fixed highlighting when Content-Type specifies charset. (#1242)
    • Fixed an unexpected crash when --raw is used with --chunked. (#1253)
    • Changed the default Windows theme from fruity to auto. (#1266)

    → Join our Discord community: → Install HTTPie: → Learn more:

    Source code(tar.gz)
    Source code(zip)
  • 2.6.0(Oct 14, 2021)

    Blog post: What’s new in HTTPie 2.6.0

    • Added support for formatting & coloring of JSON bodies preceded by non-JSON data (e.g., an XXSI prefix). (#1130)
    • Added charset auto-detection when Content-Type doesn’t include it. (#1110, #1168)
    • Added --response-charset to allow overriding the response encoding for terminal display purposes. (#1168)
    • Added --response-mime to allow overriding the response mime type for coloring and formatting for the terminal. (#1168)
    • Added the ability to silence warnings through using -q or --quiet twice (e.g. -qq) (#1175)
    • Added installed plugin list to --debug output. (#1165)
    • Fixed duplicate keys preservation in JSON data. (#1163)

    → Join our Discord community: → Install HTTPie: → Learn more:

    Source code(tar.gz)
    Source code(zip)
  • 2.5.0(Sep 6, 2021)

    Blog post: What’s new in HTTPie 2.5.0

    • Added --raw to allow specifying the raw request body without extra processing as an alternative to stdin. (#534)
    • Added support for XML formatting. (#1129)
    • Added internal support for file-like object responses to improve adapter plugin support. (#1094)
    • Fixed --continue --download with a single byte to be downloaded left. (#1032)
    • Fixed --verbose HTTP 307 redirects with streamed request body. (#1088)
    • Fixed handling of session files with Cookie: followed by other headers. (#1126)

    → Join our Discord community: → Install HTTPie: → Learn more:

    Source code(tar.gz)
    Source code(zip)
  • 2.4.0(Feb 6, 2021)

    HTTPie /aitch-tee-tee-pie/ CLI is a human-friendly CLI HTTP client for the API era.

    The 2.4.0 release introduces the following improvements:

    • Added support for --session cookie expiration based on Set-Cookie: max-age=<n>. (#1029)
    • Show a --check-status warning with --quiet as well, not only when the output is redirected. (#1026)
    • Fixed upload with --session (#1020).
    • Fixed a missing blank line between request and response (#1006).

    Join our Discord community: Install HTTPie: Learn more:

    Source code(tar.gz)
    Source code(zip)
  • 2.3.0(Oct 25, 2020)

    • Added support for streamed uploads (#201).
    • Added support for multipart upload streaming (#684).
    • Added support for body-from-file upload streaming (http @file).
    • Added --chunked to enable chunked transfer encoding (#753).
    • Added --multipart to allow multipart/form-data encoding for non-file --form requests as well.
    • Added support for preserving field order in multipart requests (#903).
    • Added --boundary to allow a custom boundary string for multipart/form-data requests.
    • Added support for combining cookies specified on the CLI and in a session file (#932).
    • Added out of the box SOCKS support with no extra installation (#904).
    • Added --quiet, -q flag to enforce silent behaviour.
    • Fixed the handling of invalid expires dates in Set-Cookie headers (#963).
    • Removed Tox testing entirely (#943).

    HTTPie /aitch-tee-tee-pie/ CLI is a user-friendly command-line HTTP client for the API era. It comes with JSON support, syntax highlighting, persistent sessions, wget-like downloads, plugins, and more.

    Learn more: Install HTTPie:

    Source code(tar.gz)
    Source code(zip)
  • 2.2.0(Jun 18, 2020)

    • Added support for custom content types for uploaded files (#927, #668).
    • Added support for $XDG_CONFIG_HOME (#920).
    • Added support for Set-Cookie-triggered cookie expiration (#853).
    • Added --format-options to allow disabling sorting, changing JSON indent size, etc. (#128)
    • Added --sorted and --unsorted shortcuts for (un)setting all sorting-related --format-options. (#128)
    • Added --ciphers to allow configuring OpenSSL ciphers (#870).
    • Added netrc support for auth plugins. Enabled for --auth-type=basic and digest, 3rd parties may opt in (#718, #719, #852, #934).
    • Fixed built-in plugins-related circular imports (#925).
    Source code(tar.gz)
    Source code(zip)
  • 2.1.0(Apr 18, 2020)

    • Added --path-as-is to bypass dot segment (/../ or /./) URL squashing (#895).
    • Changed the default Accept header value for JSON requests from application/json, */* to application/json, */*;q=0.5 to clearly indicate preference (#488).
    • Fixed --form file upload mixed with redirected stdin error handling (#840).
    Source code(tar.gz)
    Source code(zip)
  • 2.0.0(Jan 12, 2020)

    • Removed Python 2.7 support (Python 3.6+ is now required).
    • Added --offline to allow building an HTTP request and printing it but not actually sending it over the network.
    • Replaced the old collect-all-then-process handling of HTTP communication with one-by-one processing of each HTTP request or response as they become available. This means that you can see headers immediately, see what is being sent even if the request fails, etc.
    • Removed automatic config file creation to avoid concurrency issues.
    • Removed the default 30-second connection --timeout limit.
    • Removed Python’s default limit of 100 response headers.
    • Added --max-headers to allow setting the max header limit.
    • Added --compress to allow request body compression.
    • Added --ignore-netrc to allow bypassing credentials from .netrc.
    • Added https alias command with https:// as the default scheme.
    • Added $ALL_PROXY documentation.
    • Added type annotations throughout the codebase.
    • Added tests/ to the PyPi package for the convenience of downstream package maintainers.
    • Fixed an error when stdin was a closed fd.
    • Improved --debug output formatting.
    Source code(tar.gz)
    Source code(zip)
  • 1.0.3(Aug 26, 2019)

    Fixed CVE-2019-10751 — the way the output filename is generated for --download requests without --output resulting in a redirect has been changed to only consider the initial URL as the base for the generated filename, and not the final one. This fixes a potential security issue under the following scenario:

    1. A --download request with no explicit --output is made (e.g., $ http -d, instructing HTTPie to generate the output filename from the Content-Disposition response header, or from the URL if the header is not provided.
    2. The server handling the request has been modified by an attacker and instead of the expected response the URL returns a redirect to another URL, e.g.,, whose response does not provide a Content-Disposition header (i.e., the base for the generated filename becomes .bash_profile instead of file.txt).
    3. Your current directory doesn’t already contain .bash_profile (i.e., no unique suffix is added to the generated filename).
    4. You don’t notice the potentially unexpected output filename as reported by HTTPie in the console output (e.g., Downloading 100.00 B to ".bash_profile").
    Source code(tar.gz)
    Source code(zip)
  • 1.0.2(Nov 14, 2018)

  • 1.0.1(Nov 14, 2018)

  • 1.0.0(Nov 2, 2018)

    • Added --style=auto which follows the terminal ANSI color styles.
    • Added support for selecting TLS 1.3 via --ssl=tls1.3 (available once implemented in upstream libraries).
    • Added true/false as valid values for --verify (in addition to yes/no) and the boolean value is case-insensitive.
    • Changed the default --style from solarized to auto (on Windows it stays fruity).
    • Fixed default headers being incorrectly case-sensitive.
    • Removed Python 2.6 support.
    Source code(tar.gz)
    Source code(zip)
  • 0.9.9(Jul 22, 2018)

  • 0.9.8(Dec 8, 2016)

    • Extended auth plugin API.
    • Added exit status code 7 for plugin errors.
    • Added support for curses-less Python installations.
    • Fixed REQUEST_ITEM arg incorrectly being reported as required.
    • Improved CTRL-C interrupt handling.
    • Added the standard exit status code 130 for keyboard interrupts.
    Source code(tar.gz)
    Source code(zip)
  • 0.9.6(Aug 13, 2016)

    • Added Python 3 as a dependency for Homebrew installations to ensure some of the newer HTTP features work out of the box for macOS users (starting with HTTPie 0.9.4.).
    • Added the ability to unset a request header with Header:, and send an empty value with Header;.
    • Added --default-scheme <URL_SCHEME> to enable things like $ alias https='http --default-scheme=https.
    • Added -I as a shortcut for --ignore-stdin.
    • Added fish shell completion (located in extras/ in the Github repo).
    • Updated requests to 2.10.0 so that SOCKS support can be added via pip install requests[socks].
    • Changed the default JSON Accept header from application/json to application/json, */*.
    • Changed the pre-processing of request HTTP headers so that any leading and trailing whitespace is removed.
    Source code(tar.gz)
    Source code(zip)
  • 0.9.4(Jul 1, 2016)

    • Added Content-Type of files uploaded in multipart/form-data requests
    • Added --ssl=<PROTOCOL> to specify the desired SSL/TLS protocol version to use for HTTPS requests.
    • Added JSON detection with --json, -j to work around incorrect Content-Type
    • Added --all to show intermediate responses such as redirects (with --follow)
    • Added --history-print, -P WHAT to specify formatting of intermediate responses
    • Added --max-redirects=N (default 30)
    • Added -A as short name for --auth-type
    • Added -F as short name for --follow
    • Removed the implicit_content_type config option (use "default_options": ["--form"] instead)
    • Redirected stdout doesn't trigger an error anymore when --output FILE is set
    • Changed the default --style back to solarized for better support of light and dark terminals
    • Improved --debug output
    • Fixed --session when used with --download
    • Fixed --download to trim too long filenames before saving the file
    • Fixed the handling of Content-Type with multiple +subtype parts
    • Removed the XML formatter as the implementation suffered from multiple issues
    Source code(tar.gz)
    Source code(zip)
  • 0.9.3(Jan 1, 2016)

    • Changed the default color --style from solarized to monokai
    • Added basic Bash autocomplete support (need to be installed manually)
    • Added request details to connection error messages
    • Fixed 'requests.packages.urllib3' has no attribute 'disable_warnings' errors that occurred in some installations
    • Fixed colors and formatting on Windows
    • Fixed --auth prompt on Windows
    Source code(tar.gz)
    Source code(zip)
  • 0.9.2(Feb 24, 2015)

  • 0.9.1(Feb 7, 2015)

  • 0.9.0(Jan 31, 2015)

    • Added --cert and --cert-key parameters to specify a client side certificate and private key for SSL
    • Improved unicode support.
    • Improved terminal color depth detection via curses.
    • To make it easier to deal with Windows paths in request items, \ now only escapes special characters (the ones that are used as key-value separators by HTTPie).
    • Switched from unittest to pytest.
    • Added Python wheel suppor.
    • Various test suite improvements.
    • Added CONTRIBUTING_.
    • Fixed User-Agent overwriting when used within a session.
    • Fixed handling of empty passwords in URL credentials.
    • Fixed multiple file uploads with the same form field name.
    • Fixed --output=/dev/null on Linux.
    • Miscellaneous bugfixes.
    Source code(tar.gz)
    Source code(zip)
  • 0.8.0(Jan 25, 2014)

  • 0.7.1(Feb 1, 2015)

  • 0.7.0(Feb 1, 2015)

  • 0.6.0(Feb 1, 2015)

    • XML data is now formatted.
    • --session and --session-read-only now also accept paths to session files (eg. http --session=/tmp/session.json
    Source code(tar.gz)
    Source code(zip)
  • 0.5.1(Feb 1, 2015)

API tools for humans. We’re hiring —
A command line tool (and Python library) for archiving Twitter JSON

A command line tool (and Python library) for archiving Twitter JSON

Documenting the Now 1.3k Nov 18, 2022
Command-line tool for looking up colors and palettes.

Colorpedia Colorpedia is a command-line tool for looking up colors, shades and palettes. Supported color models: HEX, RGB, HSL, HSV, CMYK. Requirement

Joohwan Oh 280 Nov 12, 2022
A Python command-line utility for validating that the outputs of a given Declarative Form Azure Portal UI JSON template map to the input parameters of a given ARM Deployment Template JSON template

A Python command-line utility for validating that the outputs of a given Declarative Form Azure Portal UI JSON template map to the input parameters of a given ARM Deployment Template JSON template

Glenn Musa 1 Feb 3, 2022
Modern line-oriented terminal emulator without support for TUIs.

Modern line-oriented terminal emulator without support for TUIs.

null 10 Jun 12, 2022
🌈 Lightweight Python package that makes it easy and fast to print terminal messages in colors. 🌈

?? Colorist for Python ?? Lightweight Python package that makes it easy and fast to print terminal messages in colors. Prerequisites Python 3.9 or hig

Jakob Bagterp 1 Feb 5, 2022
frogtrade9000 - a command-line Rich client for the freqtrade REST API

frogtrade9000 - a command-line Rich client for the freqtrade REST API I found FreqUI too cumbersome and slow on my Raspberry Pi 400 when running multi

Robert Davey 75 Nov 12, 2022
GetRepo-py is a command line client that queries GitHub API and searches repositories by given arguments

GetRepo-py is a command line client that queries GitHub API and searches repositories by given arguments

Davidcin 3 Feb 14, 2022
A command line interface to interact with the Hypixel api allowing the user to get stats, leaderboards, etc

HyConsole is a way to get data on players and leaderboards from the Hypixel Minecraft server from the command line. Keep in mind I have no a

null 1 Feb 14, 2022
A simple cli utility for importing or exporting dashboard json definitions using the Grafana HTTP API.

grafana-dashboard-manager A simple cli utility for importing or exporting dashboard json definitions using the Grafana HTTP API. This may be useful fo

Beam Connectivity 28 Nov 3, 2022
Easily turn single threaded command line applications into a fast, multi-threaded application with CIDR and glob support.

Easily turn single threaded command line applications into a fast, multi-threaded application with CIDR and glob support.

Michael Skelton 1k Nov 20, 2022
eBay's TSV Utilities: Command line tools for large, tabular data files. Filtering, statistics, sampling, joins and more.

Command line utilities for tabular data files This is a set of command line utilities for manipulating large tabular data files. Files of numeric and

eBay 1.3k Nov 17, 2022
Command line tool to automate transforming the effects of one color profile to another, possibly more standard one.

Finished rendering the frames of that animation, and now the colors look washed out and ugly? This terminal program will solve exactly that.

Eric Xue 1 Jan 26, 2022
A command-line based, minimal torrent streaming client made using Python and Webtorrent-cli.

ABOUT A command-line based, minimal torrent streaming client made using Python and Webtorrent-cli. Installation pip install -r requirements.txt It use

Janardon Hazarika 16 Aug 10, 2022
Command line client for Audience Insights

Dynamics 365 Audience Insights CLI The AuI CLI is a command line tool for Dynamics 365 Audience Insights. It is based on the customerinsights Python l

Microsoft 7 Aug 10, 2022
Splitgraph command line client and python library

Splitgraph Overview Splitgraph is a tool for building, versioning and querying reproducible datasets. It's inspired by Docker and Git, so it feels fam

Splitgraph 312 Oct 25, 2022
RSS reader client for CLI (Command Line Interface),

rReader is RSS reader client for CLI(Command Line Interface)

Lee JunHaeng 9 Aug 9, 2022
A cd command that learns - easily navigate directories from the command line

NAME autojump - a faster way to navigate your filesystem DESCRIPTION autojump is a faster way to navigate your filesystem. It works by maintaining a d

William Ting 14.4k Nov 20, 2022
AML Command Transfer. A lightweight tool to transfer any command line to Azure Machine Learning Services

AML Command Transfer (ACT) ACT is a lightweight tool to transfer any command from the local machine to AML or ITP, both of which are Azure Machine Lea

Microsoft 11 Aug 10, 2022