mitmproxy/docs/features/clientreplay.rst

.. _clientreplay:

Client-side replay
==================

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
:ref:`anticache` option, to make sure the server responds with complete data.

================== ===========
command-line       ``-c path``
mitmproxy shortcut :kbd:`R` then :kbd:`c`
================== ===========
docs++ 2015-09-05 23:37:15 +00:00			`.. _clientreplay:`

			`Client-side replay`
			`==================`

			`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`
			:ref:`anticache` option, to make sure the server responds with complete data.

docs: remove option directive inserting " .. option::" tags create ugly markup, so we just ditch this entirely and continue using refs. 2016-06-07 02:08:46 +00:00			`================== ===========`
			command-line ``-c path``
docs: cleanups improvements and fighting sphinx - Hide links to internal code listings, and link to github instead - Improve formatting of code/example captions - Fix outdated documentation of command-line options - Complete documentation of all events + improved formatting - tcp_open -> tcp_start, tcp_close -> tcp_end to reduce confusion 2016-10-11 21:57:05 +00:00			mitmproxy shortcut :kbd:`R` then :kbd:`c`
docs: remove option directive inserting " .. option::" tags create ugly markup, so we just ditch this entirely and continue using refs. 2016-06-07 02:08:46 +00:00			`================== ===========`