2011-03-16 02:27:26 +00:00
|
|
|
|
|
|
|
|
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.
|
|
|
|
|
|
2011-08-04 22:23:32 +00:00
|
|
|
You may want to use client-side replay in conjunction with the
|
2013-01-02 01:02:41 +00:00
|
|
|
[anticache](@!urlTo("anticache.html")!@) option, to make sure the server
|
|
|
|
|
responds with complete data.
|
2013-01-02 08:57:39 +00:00
|
|
|
|
|
|
|
|
|
|
|
|
|
<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>
|
