diff options
| author | Maximilian Hils <git@maximilianhils.com> | 2015-09-07 10:30:40 +0200 |
|---|---|---|
| committer | Maximilian Hils <git@maximilianhils.com> | 2015-09-07 10:30:40 +0200 |
| commit | 31ee4607c892f85c5d139e54acbc3ca4f9fb6bcb (patch) | |
| tree | 873629c79b60b0ac0a7dbb458fe6ad82c2e042ef /doc-src/features/clientreplay.html | |
| parent | b4013659a81a48908eb3e060f04143ba1f9689bb (diff) | |
| download | mitmproxy-31ee4607c892f85c5d139e54acbc3ca4f9fb6bcb.tar.gz mitmproxy-31ee4607c892f85c5d139e54acbc3ca4f9fb6bcb.tar.bz2 mitmproxy-31ee4607c892f85c5d139e54acbc3ca4f9fb6bcb.zip | |
remove old docs
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> |