skip to navigation
skip to content

fallixy 0.18.1

(Fallible version with extras)An interactive, MITM HTTP proxy for penetration testers and software developers.


|travis| |appveyor| |coverage| |latest_release| |python_versions|

This repository contains the **mitmproxy** and **pathod** projects, as well as
their shared networking library, **netlib**.

``mitmproxy`` is an interactive, SSL-capable intercepting proxy with a console

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

``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
and pathod websites.

|mitmproxy_site| |pathod_site|

The latest documentation for mitmproxy is also available on ReadTheDocs.


Join our discussion forum on Discourse to ask questions, help
each other solve problems, and come up with new ideas for the project.


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



The installation instructions are `here <http:"" en="" stable="" install.html="">`_.
If you want to contribute changes, keep on reading.


To get started hacking on mitmproxy, make sure you have Python_ 3.5.x or above with
virtualenv_ installed (you can find installation instructions for virtualenv
`here <http:"" en="" latest=""/>`_). Then do the following:

.. code-block:: text

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, netlib and pathod - are installed as
"editable", so any changes to the source in the repository will be reflected
live in the virtualenv.

To confirm that you're up and running, activate the virtualenv, and run the
mitmproxy test suite:

.. code-block:: text

. venv/bin/activate # venv\Scripts\activate on Windows

Note that 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:: text

mitmdump --version

For convenience, the project includes an autoenv_ file (`.env`_) that
auto-activates the virtualenv when you cd into the mitmproxy directory.


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

.. code-block:: text


Please ensure that all patches are accompanied by matching changes in the test
suite. The project tries to maintain 100% test coverage.

You can also use `tox` to run a full suite of tests in Python 2.7 and 3.5,
including a quick test to check documentation and code linting.

The following tox environments are relevant for local testing:

.. code-block:: text

tox -e py27 # runs all tests with Python 2.7
tox -e py35 # runs all tests with Python 3.5
tox -e docs # runs a does-it-compile check on the documentation
tox -e lint # runs the linter for coding style checks

We support Python 2.7 and 3.5, so please make sure all tests pass in both
environments. Running `tox` ensures all necessary tests are executed.


The mitmproxy documentation is build using Sphinx_, which is installed
automatically if you set up a development environment as described above. After
installation, you can render the documentation like this:

.. code-block:: text

cd docs
make clean
make html
make livehtml

The last command invokes `sphinx-autobuild`_, which watches the Sphinx directory and rebuilds
the documentation when a change is detected.


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. We are using this command to check for style compliance:

.. code-block:: text

flake8 --jobs 8 --count mitmproxy netlib pathod examples test

.. |mitmproxy_site| image::

.. |pathod_site| image::

.. |mitmproxy_docs| image::
:alt: mitmproxy documentation

.. |mitmproxy_discourse| image::
:alt: Discourse: mitmproxy

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

.. |travis| image::
:alt: Travis Build Status

.. |appveyor| image::
:alt: Appveyor Build Status

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

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

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

.. _Python:
.. _virtualenv:
.. _autoenv:
.. _.env:
.. _Sphinx:
.. _sphinx-autobuild:
.. _issue_tracker:
.. _PEP8:
.. _Google Style Guide:  
File Type Py Version Uploaded on Size
fallixy-0.18.1-py2.py3-none-any.whl (md5) Python Wheel py2.py3 2016-12-10 1MB