aboutsummaryrefslogtreecommitdiffstats
path: root/doc-src/features/clientreplay.html
diff options
context:
space:
mode:
authorAldo Cortesi <aldo@nullcube.com>2014-01-27 14:16:23 +1300
committerAldo Cortesi <aldo@nullcube.com>2014-01-27 14:16:23 +1300
commitf47d89ff4e710f6d2df755fe526e91a5cf236cfa (patch)
tree61c35a397e569619ae7022fb006279d86a0d88eb /doc-src/features/clientreplay.html
parent47c7e37723b416605f232cd85818f41d865a9f85 (diff)
downloadmitmproxy-f47d89ff4e710f6d2df755fe526e91a5cf236cfa.tar.gz
mitmproxy-f47d89ff4e710f6d2df755fe526e91a5cf236cfa.tar.bz2
mitmproxy-f47d89ff4e710f6d2df755fe526e91a5cf236cfa.zip
Revert "Move the doc tree out into its own repo."
This reverts commit 8f88fcedd601c0033b4469b66626a83011879baf.
Diffstat (limited to 'doc-src/features/clientreplay.html')
-rw-r--r--doc-src/features/clientreplay.html22
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>