From 80af3589e244b7d772ab649462f1c27070d15284 Mon Sep 17 00:00:00 2001 From: Maximilian Hils Date: Sun, 14 Sep 2014 15:22:24 +0200 Subject: docs: make sure that inline script devs don't miss the examples --- doc-src/scripting/inlinescripts.html | 11 +++++++++-- 1 file changed, 9 insertions(+), 2 deletions(-) (limited to 'doc-src/scripting/inlinescripts.html') diff --git a/doc-src/scripting/inlinescripts.html b/doc-src/scripting/inlinescripts.html index eef4e440..2c3e0d6f 100644 --- a/doc-src/scripting/inlinescripts.html +++ b/doc-src/scripting/inlinescripts.html @@ -21,6 +21,12 @@ We can now run this script using mitmdump or mitmproxy as follows: The new header will be added to all responses passing through the proxy. +## Example Scripts + +mitmproxy comes with a variety of example inline scripts, which demonstrate +many basic tasks. We encourage you to either browse them locally or in our +[GitHub repo](https://github.com/mitmproxy/mitmproxy/tree/master/examples). + ## Events @@ -129,8 +135,9 @@ The main classes you will deal with in writing mitmproxy scripts are: -The canonical API documentation is the code. You can view the API documentation -using pydoc (which is installed with Python by default), like this: +The canonical API documentation is the code, which you can browse locally or in our +[GitHub repo](https://github.com/mitmproxy/mitmproxy). +You can view the API documentation using pydoc (which is installed with Python by default), like this: 
 > pydoc libmproxy.protocol.http.HTTPRequest
-- 
cgit v1.2.3