aboutsummaryrefslogtreecommitdiffstats
path: root/docs/features/clientreplay.rst
diff options
context:
space:
mode:
authorMaximilian Hils <git@maximilianhils.com>2015-09-06 01:37:15 +0200
committerMaximilian Hils <git@maximilianhils.com>2015-09-06 01:37:15 +0200
commit853cd810757a02252402da22ae77cab77c5a3fb6 (patch)
tree8b6b3c0985b8bf3fa1b3f4dd65ea1a53838a4bea /docs/features/clientreplay.rst
parent23e8260a99cc757ce0f66c044d832b138217e8e5 (diff)
downloadmitmproxy-853cd810757a02252402da22ae77cab77c5a3fb6.tar.gz
mitmproxy-853cd810757a02252402da22ae77cab77c5a3fb6.tar.bz2
mitmproxy-853cd810757a02252402da22ae77cab77c5a3fb6.zip
docs++
Diffstat (limited to 'docs/features/clientreplay.rst')
-rw-r--r--docs/features/clientreplay.rst18
1 files changed, 18 insertions, 0 deletions
diff --git a/docs/features/clientreplay.rst b/docs/features/clientreplay.rst
new file mode 100644
index 00000000..b8ca989e
--- /dev/null
+++ b/docs/features/clientreplay.rst
@@ -0,0 +1,18 @@
+.. _clientreplay:
+
+Client-side replay
+==================
+
+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
+:ref:`anticache` option, to make sure the server responds with complete data.
+
+================== =================
+command-line :option:`-c path`
+mitmproxy shortcut :kbd:`c`
+================== ================= \ No newline at end of file