diff options
| author | Aldo Cortesi <aldo@nullcube.com> | 2014-01-22 13:33:02 +1300 |
|---|---|---|
| committer | Aldo Cortesi <aldo@nullcube.com> | 2014-01-22 13:33:02 +1300 |
| commit | 8f88fcedd601c0033b4469b66626a83011879baf (patch) | |
| tree | 878b2c737f2483f52e7c222541483773af1c152a /doc-src/features/clientreplay.html | |
| parent | 7ddc941116852b191d80643af70af90a6fd8849c (diff) | |
| download | mitmproxy-8f88fcedd601c0033b4469b66626a83011879baf.tar.gz mitmproxy-8f88fcedd601c0033b4469b66626a83011879baf.tar.bz2 mitmproxy-8f88fcedd601c0033b4469b66626a83011879baf.zip | |
Move the doc tree out into its own repo.
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> |