From 9af516b14b50fe11dce7c93516aef2cec7d5dadd Mon Sep 17 00:00:00 2001 From: Aldo Cortesi Date: Wed, 16 Mar 2011 15:27:26 +1300 Subject: Documentation. --- doc-src/clientreplay.html | 11 +++++++++++ 1 file changed, 11 insertions(+) create mode 100644 doc-src/clientreplay.html (limited to 'doc-src/clientreplay.html') 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. + -- cgit v1.2.3