aboutsummaryrefslogtreecommitdiffstats
path: root/doc-src/clientreplay.html
diff options
context:
space:
mode:
Diffstat (limited to 'doc-src/clientreplay.html')
-rw-r--r--doc-src/clientreplay.html9
1 files changed, 6 insertions, 3 deletions
diff --git a/doc-src/clientreplay.html b/doc-src/clientreplay.html
index efc632f6..d4b1c3ff 100644
--- a/doc-src/clientreplay.html
+++ b/doc-src/clientreplay.html
@@ -1,11 +1,14 @@
+- command-line: _-c path_
+- mitmproxy shortcut: _c_
+
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__
-option. This will modify requests to remove headers (e.g. if-modified-since)
-that might cause a server to reply with a 304-not-modified.
+You may want to use client-side replay in conjunction with the
+[anticache](@!urlTo("anticache.html")!@) option.
+