Github url


by mitmproxy

mitmproxy /mitmproxy

An interactive TLS-capable intercepting HTTP proxy for penetration testers and software developers.

19.3K Stars 2.5K Forks Last release: 3 months ago (v5.1.1) MIT License 8.6K Commits 56 Releases

Available items

No Items, yet!

The developer of this repository has not created any items for sale yet. Need a bug fixed? Help with integration? A different license? Create a request here:

mitmproxy ^^^^^^^^^

|ci_status| |coverage| |latest_release| |python_versions|

This repository contains the mitmproxy and pathod projects.


is an interactive, SSL/TLS-capable intercepting proxy with a console interface for HTTP/1, HTTP/2, and WebSockets.


is the command-line version of mitmproxy. Think tcpdump for HTTP.


is a web-based interface for mitmproxy.




are perverse HTTP client and server applications designed to let you craft almost any conceivable HTTP request, including ones that creatively violate the standards.

Documentation & Help

General information, tutorials, and precompiled binaries can be found on the mitmproxy website.


The documentation for mitmproxy is available on our website:

|mitmproxy_docs_stable| |mitmproxy_docs_master|

If you have questions on how to use mitmproxy, please ask them on StackOverflow!


Join our developer chat on Slack if you would like to contribute to mitmproxy itself.



The installation instructions are

here <https:></https:>

__. If you want to contribute changes, keep on reading.


As an open source project, mitmproxy welcomes contributions of all forms. If you would like to bring the project forward, please consider contributing in the following areas:

  • Maintenance: We are incredibly thankful for individuals who are stepping up and helping with maintenance. This includes (but is not limited to) triaging issues, reviewing pull requests and picking up stale ones, helping out other users on StackOverflow_, creating minimal, complete and verifiable examples or test cases for existing bug reports, updating documentation, or fixing minor bugs that have recently been reported.
  • Code Contributions: We actively mark issues that we consider are
    good first contributions
    _. If you intend to work on a larger contribution to the project, please come talk to us first.

Development Setup

To get started hacking on mitmproxy, please install a recent version of Python (we require at least 3.6). The following commands should work on your system:

.. code-block:: bash

python3 --version python3 -m pip --help python3 -m venv --help

If all of this run successfully, do the following:

.. code-block:: bash

git clone cd mitmproxy ./ # "powershell .\dev.ps1" on Windows

The dev script will create a


_ environment in a directory called "venv" and install all mandatory and optional dependencies into it. The primary mitmproxy components - mitmproxy and pathod - are installed as "editable", so any changes to the source in the repository will be reflected live in the virtualenv.

The main executables for the project -








, and

  • are all created within the virtualenv. After activating the virtualenv, they will be on your $PATH, and you can run them like any other command:

.. code-block:: bash

. venv/bin/activate # "venv\Scripts\activate" on Windows mitmdump --version


If you've followed the procedure above, you already have all the development requirements installed, and you can run the basic test suite with tox_:

.. code-block:: bash

tox -e py # runs Python tests

Our CI system has additional tox environments that are run on every pull request and branch on GitHub.

For speedier testing, we recommend you run


_ directly on individual test files or folders:

.. code-block:: bash

cd test/mitmproxy/addons pytest --cov mitmproxy.addons.anticache --cov-report term-missing --looponfail test\

Pytest does not check the code style, so you want to run

tox -e flake8

again before committing.

Please ensure that all patches are accompanied by matching changes in the test suite. The project tries to maintain 100% test coverage and enforces this strictly for some parts of the codebase.


The following tools are required to build the mitmproxy docs:

  • Hugo_ (the extended version
    is required)
  • modd_

.. code-block:: bash

cd docs modd

Code Style

Keeping to a consistent code style throughout the project makes it easier to contribute and collaborate. Please stick to the guidelines in


_ and the

Google Style Guide

_ unless there's a very good reason not to.

This is automatically enforced on every PR. If we detect a linting error, the PR checks will fail and block merging. You can run our lint checks yourself with the following commands:

.. code-block:: bash

tox -e flake8 tox -e mypy # checks static types

.. |mitmproxy_site| image:: :target: :alt:

.. |mitmproxy_docs_stable| image:: :target: :alt: mitmproxy documentation stable

.. |mitmproxy_docs_master| image:: :target: :alt: mitmproxy documentation master

.. |mitmproxy_stackoverflow| image:: :target: :alt: StackOverflow: mitmproxy

.. |slack| image:: :target: :alt: Slack Developer Chat

.. |ci_status| image:: :target: :alt: Continuous Integration Status

.. |coverage| image:: :target: :alt: Coverage Status

.. |latest_release| image:: :target: :alt: Latest Version

.. |python_versions| image:: :target: :alt: Supported Python versions

.. _virtualenv: .. _


: .. _tox: .. _Hugo: .. _modd: .. _PEP8: .. _

Google Style Guide

: .. _StackOverflow: .. _

good first contributions


We use cookies. If you continue to browse the site, you agree to the use of cookies. For more information on our use of cookies please see our Privacy Policy.