forked from (bubble branch has our minor changes)
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
Maximilian Hils 735b8e35c9
Merge pull request #3809 from mhils/issue-3801
4 years ago
.github Revert "ci: run on tags" 4 years ago
docs Fix broken link with link to similar addon. This fixes issue #3775. 4 years ago
examples Address lint 4 years ago
mitmproxy Merge pull request #3801 from mitmproxy/issue-3794 4 years ago
pathod update mypy 4 years ago
release pyinstaller: add publicsuffix2 hook 4 years ago
test fix #3801 4 years ago
web Fix wording for ssl_insecure option on mitmweb 4 years ago
.codecov.yml hide codecov.yml 8 years ago
.gitattributes Use Github Actions for CI (#3713) 4 years ago
.gitignore bump dependencies 4 years ago
CHANGELOG update CHANGELOG for 5.0.1 4 years ago
LICENSE GPLv3 -> MIT 11 years ago Revert "Remove" 6 years ago
README.rst remove unused hyperlink in README.rst 4 years ago
dev.ps1 Update dev.ps1 6 years ago always use 'venv' as virtualenv folder 7 years ago
requirements.txt fix requirements 7 years ago
setup.cfg Merge pull request #3693 from typoon/fix-command-bar-issue-3259 4 years ago bump urwid 4 years ago
tox.ini Use Github Actions for CI (#3713) 4 years ago



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

This repository contains the **mitmproxy** and **pathod** projects.

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

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

``mitmweb`` is a web-based interface for mitmproxy.

``pathoc`` and ``pathod`` 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 <>`__.
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 `virtualenv`_ 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 - ``mitmdump``, ``mitmproxy``,
``mitmweb``, ``pathod``, and ``pathoc`` - 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 full test suite with tox_:

.. code-block:: bash

tox -e py # runs Python tests
tox -e lint # checks code style

For speedier testing, we recommend you run `pytest`_ directly on individual test files or folders:

.. code-block:: bash

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

Pytest does not check the code style, so you want to run ``tox -e lint`` 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_
- modd_
- yarn_

.. code-block:: bash

cd docs

Code Style

Keeping to a consistent code style throughout the project makes it easier to
contribute and collaborate. Please stick to the guidelines in
`PEP8`_ 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 command:

.. code-block:: bash

tox -e lint

.. |mitmproxy_site| image::

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

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

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

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

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

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

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

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

.. _virtualenv:
.. _`pytest`:
.. _tox:
.. _Hugo:
.. _modd:
.. _yarn:
.. _PEP8:
.. _`Google Style Guide`:
.. _StackOverflow:
.. _`good first contributions`: