diff options
author | kira0204 <rshtmudgal@gmail.com> | 2018-02-24 12:42:21 +0530 |
---|---|---|
committer | kira0204 <rshtmudgal@gmail.com> | 2018-02-24 12:42:21 +0530 |
commit | 8209b89d41bdfc3b6a9a3dd5d9054b02722e0d4f (patch) | |
tree | 5691f1dd11ac1b2a98e57ed06252ff7dc40cd555 /docs/features/serverreplay.rst | |
parent | 69dbd1da61e6e452da63c63fba1d810b269f459d (diff) | |
parent | eee109117f956600261bc938be52040d1474a97f (diff) | |
download | mitmproxy-8209b89d41bdfc3b6a9a3dd5d9054b02722e0d4f.tar.gz mitmproxy-8209b89d41bdfc3b6a9a3dd5d9054b02722e0d4f.tar.bz2 mitmproxy-8209b89d41bdfc3b6a9a3dd5d9054b02722e0d4f.zip |
Merge branch 'master' of https://github.com/kira0204/mitmproxy into update-readme
Diffstat (limited to 'docs/features/serverreplay.rst')
-rw-r--r-- | docs/features/serverreplay.rst | 52 |
1 files changed, 0 insertions, 52 deletions
diff --git a/docs/features/serverreplay.rst b/docs/features/serverreplay.rst deleted file mode 100644 index aef0296e..00000000 --- a/docs/features/serverreplay.rst +++ /dev/null @@ -1,52 +0,0 @@ -.. _serverreplay: - -Server-side replay -================== - -Server-side replay lets us replay server responses from a saved HTTP -conversation. - -Matching requests with responses --------------------------------- - -By default, :program:`mitmproxy` excludes request headers when matching incoming -requests with responses from the replay file. This works in most circumstances, -and makes it possible to replay server responses in situations where request -headers would naturally vary, e.g. using a different user agent. -The ``--rheader headername`` command-line option allows you to override -this behaviour by specifying individual headers that should be included in matching. - - -Response refreshing -------------------- - -Simply replaying server responses without modification will often result in -unexpected behaviour. For example cookie timeouts that were in the future at -the time a conversation was recorded might be in the past at the time it is -replayed. By default, :program:`mitmproxy` refreshes server responses before sending -them to the client. The **date**, **expires** and **last-modified** headers are -all updated to have the same relative time offset as they had at the time of -recording. So, if they were in the past at the time of recording, they will be -in the past at the time of replay, and vice versa. Cookie expiry times are -updated in a similar way. - -You can turn off response refreshing using the ``--norefresh`` argument, or using -the :kbd:`O` options shortcut within :program:`mitmproxy`. - - -Replaying a session recorded in Reverse-proxy Mode --------------------------------------------------- - -If you have captured the session in reverse proxy mode, in order to replay it you -still have to specify the server URL, otherwise you may get the error: -'HTTP protocol error in client request: Invalid HTTP request form (expected authority or absolute...)'. - -During replay, when the client's requests match previously recorded requests, then the -respective recorded responses are simply replayed by mitmproxy. -Otherwise, the unmatched requests is forwarded to the upstream server. -If forwarding is not desired, you can use the --kill (-k) switch to prevent that. - -================== =========== -command-line ``-S path`` -mitmproxy shortcut :kbd:`R` then :kbd:`s` -================== =========== |