aboutsummaryrefslogtreecommitdiffstats
path: root/doc-src/features/clientreplay.html
diff options
context:
space:
mode:
authorMaximilian Hils <git@maximilianhils.com>2014-01-28 17:29:28 +0100
committerMaximilian Hils <git@maximilianhils.com>2014-01-28 17:29:28 +0100
commit1e3e0dd1271afda59ec244b64391b6579a998dce (patch)
tree5f1f617ccc8ea2b29650c10197407b1d3ecb7139 /doc-src/features/clientreplay.html
parent17f09aa0afe9695505b746c370e1c5b889c19058 (diff)
parent3aa78f9ff38471f84a471618e1a43ca02fc65b6a (diff)
downloadmitmproxy-1e3e0dd1271afda59ec244b64391b6579a998dce.tar.gz
mitmproxy-1e3e0dd1271afda59ec244b64391b6579a998dce.tar.bz2
mitmproxy-1e3e0dd1271afda59ec244b64391b6579a998dce.zip
merge master
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>