aboutsummaryrefslogtreecommitdiffstats
path: root/docs/scripting
diff options
context:
space:
mode:
authorMaximilian Hils <git@maximilianhils.com>2016-06-26 14:42:12 -0700
committerMaximilian Hils <git@maximilianhils.com>2016-06-26 14:42:12 -0700
commit588dad1bc7f28eeec2851d785387608d40e7382e (patch)
treede528c54d86793fe51a2e15fcc4302f7b83f21e5 /docs/scripting
parented9a72553df91085021cc2a9187287ac73cc458c (diff)
downloadmitmproxy-588dad1bc7f28eeec2851d785387608d40e7382e.tar.gz
mitmproxy-588dad1bc7f28eeec2851d785387608d40e7382e.tar.bz2
mitmproxy-588dad1bc7f28eeec2851d785387608d40e7382e.zip
minor docs fix
Diffstat (limited to 'docs/scripting')
-rw-r--r--docs/scripting/inlinescripts.rst2
1 files changed, 1 insertions, 1 deletions
diff --git a/docs/scripting/inlinescripts.rst b/docs/scripting/inlinescripts.rst
index 2065923d..1ee44972 100644
--- a/docs/scripting/inlinescripts.rst
+++ b/docs/scripting/inlinescripts.rst
@@ -17,7 +17,7 @@ client:
The first argument to each event method is an instance of
:py:class:`~mitmproxy.script.ScriptContext` that lets the script interact with the global mitmproxy
-state. The **response** event also gets an instance of :py:class:`~mitmproxy.script.ScriptContext`,
+state. The **response** event also gets an instance of :py:class:`~mitmproxy.models.HTTPFlow`,
which we can use to manipulate the response itself.
We can now run this script using mitmdump or mitmproxy as follows: