diff options
| author | Aldo Cortesi <aldo@nullcube.com> | 2011-08-05 10:23:32 +1200 |
|---|---|---|
| committer | Aldo Cortesi <aldo@nullcube.com> | 2011-08-05 10:23:32 +1200 |
| commit | 98a7aaca182ce6b879329bbaeb06efca284c6220 (patch) | |
| tree | a9afa1dae76d3206990cc49a30c2433ea6077609 /doc-src/clientreplay.html | |
| parent | ce48cb4debab8caa518ea54e36dee722aaabb8a5 (diff) | |
| download | mitmproxy-98a7aaca182ce6b879329bbaeb06efca284c6220.tar.gz mitmproxy-98a7aaca182ce6b879329bbaeb06efca284c6220.tar.bz2 mitmproxy-98a7aaca182ce6b879329bbaeb06efca284c6220.zip | |
Documentation.
Diffstat (limited to 'doc-src/clientreplay.html')
| -rw-r--r-- | doc-src/clientreplay.html | 9 |
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. + |