aboutsummaryrefslogtreecommitdiffstats
path: root/doc-src/features/clientreplay.html
diff options
context:
space:
mode:
authorMaximilian Hils <git@maximilianhils.com>2015-09-16 02:53:01 +0200
committerMaximilian Hils <git@maximilianhils.com>2015-09-16 02:53:01 +0200
commit457025df9a64f312685774cb743eeb52cd37bd3f (patch)
tree98de6633322059ac95ab50e4b2d3129aa6051b58 /doc-src/features/clientreplay.html
parent436a9ea8398e25709f139fde609aa74e8fb3f3f8 (diff)
parentc3f73552b82923e8da224529895332c44bf8dace (diff)
downloadmitmproxy-457025df9a64f312685774cb743eeb52cd37bd3f.tar.gz
mitmproxy-457025df9a64f312685774cb743eeb52cd37bd3f.tar.bz2
mitmproxy-457025df9a64f312685774cb743eeb52cd37bd3f.zip
Merge pull request #751 from mitmproxy/readthedocs
Move Docs to readthedocs
Diffstat (limited to 'doc-src/features/clientreplay.html')
-rw-r--r--doc-src/features/clientreplay.html22
1 files changed, 0 insertions, 22 deletions
diff --git a/doc-src/features/clientreplay.html b/doc-src/features/clientreplay.html
deleted file mode 100644
index 6638d078..00000000
--- a/doc-src/features/clientreplay.html
+++ /dev/null
@@ -1,22 +0,0 @@
-
-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>