mitmproxy/examples/simple/add_header_class.py

from mitmproxy import http


class AddHeader:
    def response(self, flow: http.HTTPFlow) -> None:
        flow.response.headers["newheader"] = "foo"


addons = [AddHeader()]
extend mypy example/simple 2017-04-28 21:56:14 +00:00			`from mitmproxy import http`


docs: overview, classes, arguments 2016-10-15 22:12:58 +00:00			`class AddHeader:`
extend mypy example/simple 2017-04-28 21:56:14 +00:00			`def response(self, flow: http.HTTPFlow) -> None:`
docs: overview, classes, arguments 2016-10-15 22:12:58 +00:00			`flow.response.headers["newheader"] = "foo"`


Revamp how addons work - Addons now nest, which means that addons can manage addons. This has a number of salutary effects - the scripts addon no longer has to poke into the global addons list, we no longer have to replace/remove/boot-outof parent addons when we load scripts, and this paves the way for making our top-level tools into addons themselves. - All addon calls are now wrapped in a safe execution environment where exceptions are caught, and output to stdout/stderr are intercepted and turned into logs. - We no longer support script arguments in sys.argv - creating an option properly is the only way to pass arguments. This means that all scripts are always directly controllable from interctive tooling, and that arguments are type-checked. For now, I've disabled testing of the har dump example - it needs to be moved to the new argument handling, and become a class addon. I'll address that in a separate patch. 2017-04-25 07:06:24 +00:00			`addons = [AddHeader()]`