diff options
| author | Aldo Cortesi <aldo@nullcube.com> | 2016-10-30 16:58:50 +1300 |
|---|---|---|
| committer | Aldo Cortesi <aldo@nullcube.com> | 2016-10-30 16:58:50 +1300 |
| commit | 0b2a2ad2a6c9d228e4b577fdba55cca2bd13aaaf (patch) | |
| tree | e39bf2d746e37ee4ab336b30a96bd49da178b81d /docs/scripting | |
| parent | a43cce504accf8160b69168050e097723ead1fdd (diff) | |
| download | mitmproxy-0b2a2ad2a6c9d228e4b577fdba55cca2bd13aaaf.tar.gz mitmproxy-0b2a2ad2a6c9d228e4b577fdba55cca2bd13aaaf.tar.bz2 mitmproxy-0b2a2ad2a6c9d228e4b577fdba55cca2bd13aaaf.zip | |
docs: examples/logging -> examples/context_logging
Diffstat (limited to 'docs/scripting')
| -rw-r--r-- | docs/scripting/overview.rst | 6 |
1 files changed, 3 insertions, 3 deletions
diff --git a/docs/scripting/overview.rst b/docs/scripting/overview.rst index b820538e..dfee23a5 100644 --- a/docs/scripting/overview.rst +++ b/docs/scripting/overview.rst @@ -80,13 +80,13 @@ Logging and the context Scripts should not output straight to stderr or stdout. Instead, the `log <api.html#mitmproxy.controller.Log>`_ object on the ``ctx`` contexzt module should be used, so that the mitmproxy host program can handle output -appropriately. So, mitmdump can print colorised sript output to the terminal, +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: -.. literalinclude:: ../../examples/logging.py - :caption: :src:`examples/logging.py` +.. literalinclude:: ../../examples/context_logging.py + :caption: :src:`examples/context_logging.py` :language: python The ``ctx`` module also exposes the mitmproxy master object at ``ctx.master`` |