diff options
| author | Maximilian Hils <git@maximilianhils.com> | 2014-03-10 17:01:30 +0100 |
|---|---|---|
| committer | Maximilian Hils <git@maximilianhils.com> | 2014-03-10 17:01:30 +0100 |
| commit | 9cc10630c8e0b0f249ed852299d3316ba42f128d (patch) | |
| tree | 4c711fe124c6c8ce786350f39f06680858a7e60b /doc-src/scripting | |
| parent | fe58c1c6eb16fdc14bd24843cb896b3d8a4eefc8 (diff) | |
| download | mitmproxy-9cc10630c8e0b0f249ed852299d3316ba42f128d.tar.gz mitmproxy-9cc10630c8e0b0f249ed852299d3316ba42f128d.tar.bz2 mitmproxy-9cc10630c8e0b0f249ed852299d3316ba42f128d.zip | |
update docs, fix #215
Diffstat (limited to 'doc-src/scripting')
| -rw-r--r-- | doc-src/scripting/inlinescripts.html | 28 |
1 files changed, 14 insertions, 14 deletions
diff --git a/doc-src/scripting/inlinescripts.html b/doc-src/scripting/inlinescripts.html index 7ab1c101..32a98e99 100644 --- a/doc-src/scripting/inlinescripts.html +++ b/doc-src/scripting/inlinescripts.html @@ -76,26 +76,26 @@ The main classes you will deal with in writing mitmproxy scripts are: <table class="table"> <tr> - <th>libmproxy.flow.ClientConnection</th> - <td>Describes a client connection.</td> + <th>libmproxy.proxy.server.ConnectionHandler</th> + <td>Describes a proxy client connection session. Always has a client_conn attribute, might have a server_conn attribute.</td> </tr> <tr> - <th>libmproxy.flow.ClientDisconnection</th> - <td>Describes a client disconnection.</td> + <th>libmproxy.proxy.connection.ClientConnection</th> + <td>Describes a client connection.</td> + </tr> + <tr> + <th>libmproxy.proxy.connection.ServerConnection</th> + <td>Describes a server connection.</td> </tr> <tr> - <th>libmproxy.flow.Error</th> + <th>libmproxy.protocol.primitives.Error</th> <td>A communications error.</td> </tr> <tr> - <th>libmproxy.flow.Flow</th> + <th>libmproxy.protocol.http.HTTPFlow</th> <td>A collection of objects representing a single HTTP transaction.</td> </tr> <tr> - <th>libmproxy.flow.Headers</th> - <td>HTTP headers for a request or response.</td> - </tr> - <tr> <th>libmproxy.flow.ODict</th> <td>A dictionary-like object for managing sets of key/value data. There @@ -103,15 +103,15 @@ The main classes you will deal with in writing mitmproxy scripts are: calls (used mainly for headers).</td> </tr> <tr> - <th>libmproxy.flow.Response</th> + <th>libmproxy.protocol.http.HTTPResponse</th> <td>An HTTP response.</td> </tr> <tr> - <th>libmproxy.flow.Request</th> + <th>libmproxy.protocol.http.HTTPRequest</th> <td>An HTTP request.</td> </tr> <tr> - <th>libmproxy.flow.ScriptContext</th> + <th>libmproxy.script.ScriptContext</th> <td> A handle for interacting with mitmproxy's from within scripts. </td> </tr> <tr> @@ -124,7 +124,7 @@ The canonical API documentation is the code. You can view the API documentation using pydoc (which is installed with Python by default), like this: <pre class="terminal"> -> pydoc libmproxy.flow.Request +> pydoc libmproxy.protocol.http.HTTPRequest </pre> |