diff options
| author | Aldo Cortesi <aldo@nullcube.com> | 2011-03-16 15:27:26 +1300 |
|---|---|---|
| committer | Aldo Cortesi <aldo@nullcube.com> | 2011-03-16 15:27:26 +1300 |
| commit | 9af516b14b50fe11dce7c93516aef2cec7d5dadd (patch) | |
| tree | de984156bec0b2a9429bba6a83c66a6e89edeaf7 /doc-src/clientreplay.html | |
| parent | e6ef0c3faf21971c144aaf93e6c05d98f1fe74be (diff) | |
| download | mitmproxy-9af516b14b50fe11dce7c93516aef2cec7d5dadd.tar.gz mitmproxy-9af516b14b50fe11dce7c93516aef2cec7d5dadd.tar.bz2 mitmproxy-9af516b14b50fe11dce7c93516aef2cec7d5dadd.zip | |
Documentation.
Diffstat (limited to 'doc-src/clientreplay.html')
| -rw-r--r-- | doc-src/clientreplay.html | 11 |
1 files changed, 11 insertions, 0 deletions
diff --git a/doc-src/clientreplay.html b/doc-src/clientreplay.html new file mode 100644 index 00000000..efc632f6 --- /dev/null +++ b/doc-src/clientreplay.html @@ -0,0 +1,11 @@ + +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. + |