mitmproxy/examples/simple/log_events.py

"""
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 start(opts):
    ctx.log.info("This is some informative text.")
    ctx.log.error("This is an error.")
organize examples This commit is largely based on work by Thiago Arrais (@thiagoarrais) and Shane Bradfield (@l33tLumberjack). I wasn't really able to get their PR reasonably merged onto the latest master, so I reapplied their changes manually here and did some further improvements on that. 2016-11-21 01:16:20 +00:00			`"""`
			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`


Enable custom options for addons - Add an options parameter to the start() event. This is to be used by addons on startup to add custom options. - Add a running() event that is called once the proxy is up and running. - With the new paradigm we can't log during master __init__, so add a tiny termstatus addon to print proxy status to terminal once we're running. 2017-03-09 00:52:58 +00:00			`def start(opts):`
organize examples This commit is largely based on work by Thiago Arrais (@thiagoarrais) and Shane Bradfield (@l33tLumberjack). I wasn't really able to get their PR reasonably merged onto the latest master, so I reapplied their changes manually here and did some further improvements on that. 2016-11-21 01:16:20 +00:00			`ctx.log.info("This is some informative text.")`
			`ctx.log.error("This is an error.")`