diff options
author | Maximilian Hils <git@maximilianhils.com> | 2014-01-22 16:01:31 +0100 |
---|---|---|
committer | Maximilian Hils <git@maximilianhils.com> | 2014-01-22 16:01:31 +0100 |
commit | 94e530ec4fe4378f89eea44796f31847da52ddf2 (patch) | |
tree | e8f30dc5fefd0654e4d700a01e4364f0ea25b8a0 /doc-src/features/clientreplay.html | |
parent | 1786d778194b543ae77468a716c9e15caf247180 (diff) | |
parent | 9044b8b8f534debf84de553bf1e57cd91a08ee91 (diff) | |
download | mitmproxy-94e530ec4fe4378f89eea44796f31847da52ddf2.tar.gz mitmproxy-94e530ec4fe4378f89eea44796f31847da52ddf2.tar.bz2 mitmproxy-94e530ec4fe4378f89eea44796f31847da52ddf2.zip |
merge master
Diffstat (limited to 'doc-src/features/clientreplay.html')
-rw-r--r-- | doc-src/features/clientreplay.html | 22 |
1 files changed, 0 insertions, 22 deletions
diff --git a/doc-src/features/clientreplay.html b/doc-src/features/clientreplay.html deleted file mode 100644 index 6638d078..00000000 --- a/doc-src/features/clientreplay.html +++ /dev/null @@ -1,22 +0,0 @@ - -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](@!urlTo("anticache.html")!@) option, to make sure the server -responds with complete data. - - -<table class="table"> - <tbody> - <tr> - <th width="20%">command-line</th> <td>-c path</td> - </tr> - <tr> - <th>mitmproxy shortcut</th> <td><b>c</b></td> - </tr> - </tbody> -</table> |