diff options
| author | Aldo Cortesi <aldo@nullcube.com> | 2013-01-02 21:57:39 +1300 |
|---|---|---|
| committer | Aldo Cortesi <aldo@nullcube.com> | 2013-01-02 21:57:39 +1300 |
| commit | 8e6fabd69a124cc5b5ae763b58587ee6ee6ab3da (patch) | |
| tree | 03fc66d5d94e5c82ddedd535c430cf9d71fd853a /doc-src/clientreplay.html | |
| parent | 09f664cdeafae1d9923fe5ce2c4ab3acc7757a61 (diff) | |
| download | mitmproxy-8e6fabd69a124cc5b5ae763b58587ee6ee6ab3da.tar.gz mitmproxy-8e6fabd69a124cc5b5ae763b58587ee6ee6ab3da.tar.bz2 mitmproxy-8e6fabd69a124cc5b5ae763b58587ee6ee6ab3da.zip | |
Docs - features.
Diffstat (limited to 'doc-src/clientreplay.html')
| -rw-r--r-- | doc-src/clientreplay.html | 15 |
1 files changed, 12 insertions, 3 deletions
diff --git a/doc-src/clientreplay.html b/doc-src/clientreplay.html index c94f5034..6638d078 100644 --- a/doc-src/clientreplay.html +++ b/doc-src/clientreplay.html @@ -1,7 +1,4 @@ -- command-line: _-c path_ -- mitmproxy shortcut: _c_ - Client-side replay does what it says on the tin: you provide a previously saved HTTP conversation, and mitmproxy replays the client requests one by one. Note that mitmproxy serializes the requests, waiting for a response from the server @@ -11,3 +8,15 @@ conversation, where requests may have been made concurrently. You may want to use client-side replay in conjunction with the [anticache](@!urlTo("anticache.html")!@) option, to make sure the server responds with complete data. + + +<table class="table"> + <tbody> + <tr> + <th width="20%">command-line</th> <td>-c path</td> + </tr> + <tr> + <th>mitmproxy shortcut</th> <td><b>c</b></td> + </tr> + </tbody> +</table> |