diff options
| author | Aldo Cortesi <aldo@nullcube.com> | 2013-01-03 08:25:24 +1300 |
|---|---|---|
| committer | Aldo Cortesi <aldo@nullcube.com> | 2013-01-03 08:25:24 +1300 |
| commit | 101f92b2566adea605b9db69dba29e575414cbba (patch) | |
| tree | eafcfac61972f7a18c069d098accc4ce2cf1cfea /doc-src/features/clientreplay.html | |
| parent | f578d68e555ff202a51b9f8672e540a964e31fed (diff) | |
| download | mitmproxy-101f92b2566adea605b9db69dba29e575414cbba.tar.gz mitmproxy-101f92b2566adea605b9db69dba29e575414cbba.tar.bz2 mitmproxy-101f92b2566adea605b9db69dba29e575414cbba.zip | |
Docs: move features into their own directory
Diffstat (limited to 'doc-src/features/clientreplay.html')
| -rw-r--r-- | doc-src/features/clientreplay.html | 22 |
1 files changed, 22 insertions, 0 deletions
diff --git a/doc-src/features/clientreplay.html b/doc-src/features/clientreplay.html new file mode 100644 index 00000000..6638d078 --- /dev/null +++ b/doc-src/features/clientreplay.html @@ -0,0 +1,22 @@ + +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 +before starting the next request. This might differ from the recorded +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> |