Mitmproxy has a powerful scripting API that allows you to control almost any aspect of traffic being proxied. In fact, much of mitmproxy’s own core functionality is implemented using the exact same API exposed to scripters (see mitmproxy/addons).
A simple example¶
Scripting is event driven, with named handlers on the script object called at appropriate points of mitmproxy’s operation. Here’s a complete mitmproxy script that adds a new header to every HTTP response before it is returned to the client:
from mitmproxy import http def response(flow: http.HTTPFlow) -> None: flow.response.headers["newheader"] = "foo"
All events that deal with an HTTP request get an instance of HTTPFlow, which we can use to manipulate the response itself. We can now run this script using mitmdump, and the new header will be added to all responses passing through the proxy:
>>> mitmdump -s add_header.py
In the example above, the script object is the
add_header module itself.
That is, the handlers are declared at the global level of the script. This is
great for quick hacks, but soon becomes limiting as scripts become more
When a script first starts up, the start, event is called before anything else happens. You can replace the current script object by returning it from this handler. Here’s how this looks when applied to the example above:
from mitmproxy import http class AddHeader: def response(self, flow: http.HTTPFlow) -> None: flow.response.headers["newheader"] = "foo" addons = [AddHeader()]
So here, we’re using a module-level script to “boot up” into a class instance. From this point on, the module-level script is removed from the handler chain, and is replaced by the class instance.
Logging and the context¶
Scripts should not output straight to stderr or stdout. Instead, the log object on the
ctx context module
should be used, so that the mitmproxy host program can handle output
appropriately. So, mitmdump can print colorised script output to the terminal,
and mitmproxy console can place script output in the event buffer.
Here’s how this looks:
""" It is recommended to use `ctx.log` for logging within a script. This goes to the event log in mitmproxy and to stdout in mitmdump. If you want to help us out: https://github.com/mitmproxy/mitmproxy/issues/1530 :-) """ from mitmproxy import ctx def load(l): ctx.log.info("This is some informative text.") ctx.log.error("This is an error.")
ctx module also exposes the mitmproxy master object at
for advanced usage.
Running scripts on saved flows¶
When a flow is loaded from disk, the sequence of events that the flow would have gone through on the wire is partially replayed. So, for instance, an HTTP flow loaded from disk will trigger requestheaders, request, responseheaders and response in order. We can use this behaviour to transform saved traffic using scripts. For example, we can invoke the replacer script from above on saved traffic as follows:
>>> mitmdump -dd -s "./arguments.py html fakehtml" -r saved -w changed
This command starts the
arguments script, reads all the flows from
saved transforming them in the process, then writes them all to
The mitmproxy console tool provides interactive ways to run transforming
scripts on flows - for instance, you can run a one-shot script on a single flow
| (pipe) shortcut.
The mitmproxy script mechanism is single threaded, and the proxy blocks while script handlers execute. This hugely simplifies the most common case, where handlers are light-weight and the blocking doesn’t have a performance impact. It’s possible to implement a concurrent mechanism on top of the blocking framework, and mitmproxy includes a handy example of this that is fit for most purposes. You can use it as follows:
import time from mitmproxy.script import concurrent @concurrent # Remove this and see what happens def request(flow): # You don't want to use mitmproxy.ctx from a different thread print("handle request: %s%s" % (flow.request.host, flow.request.path)) time.sleep(5) print("start request: %s%s" % (flow.request.host, flow.request.path))
Mitmproxy includes a number of helpers for testing addons. The
mitmproxy.test.taddons module contains a context helper that takes care of
setting up and tearing down the addon event context. The
mitmproxy.test.tflow module contains helpers for quickly creating test
flows. Pydoc is the canonical reference for these modules, and mitmproxy’s own
test suite is an excellent source of examples of usage. Here, for instance, is
the mitmproxy unit tests for the anticache option, demonstrating a good
cross-section of the test helpers:
from mitmproxy.test import tflow from mitmproxy.addons import anticache from mitmproxy.test import taddons class TestAntiCache: def test_simple(self): sa = anticache.AntiCache() with taddons.context() as tctx: f = tflow.tflow(resp=True) f.request.headers["if-modified-since"] = "test" f.request.headers["if-none-match"] = "test" sa.request(f) assert "if-modified-since" in f.request.headers assert "if-none-match" in f.request.headers tctx.configure(sa, anticache = True) sa.request(f) assert "if-modified-since" not in f.request.headers assert "if-none-match" not in f.request.headers