diff options
author | Ujjwal Verma <ujjwalverma1111@gmail.com> | 2017-03-11 11:14:22 +0530 |
---|---|---|
committer | Ujjwal Verma <ujjwalverma1111@gmail.com> | 2017-03-11 11:14:22 +0530 |
commit | e0382fde2f6869554d68137639e2921ceb1e63b6 (patch) | |
tree | 124bbbaf933982ecf27c0d28e64c301551f3524f /docs | |
parent | 25703f8c539fb954efb2551f6f5050018d623501 (diff) | |
download | mitmproxy-e0382fde2f6869554d68137639e2921ceb1e63b6.tar.gz mitmproxy-e0382fde2f6869554d68137639e2921ceb1e63b6.tar.bz2 mitmproxy-e0382fde2f6869554d68137639e2921ceb1e63b6.zip |
Changed docs
Diffstat (limited to 'docs')
-rw-r--r-- | docs/features/replacements.rst | 8 |
1 files changed, 4 insertions, 4 deletions
diff --git a/docs/features/replacements.rst b/docs/features/replacements.rst index 215f0ddb..d46b3a8b 100644 --- a/docs/features/replacements.rst +++ b/docs/features/replacements.rst @@ -48,13 +48,14 @@ In practice, it's pretty common for the replacement literal to be long and complex. For instance, it might be an XSS exploit that weighs in at hundreds or thousands of characters. To cope with this, there's a variation of the replacement hook specifier that lets you load the replacement text from a file. +To specify a file as replacement, prefix the file path with ``@`` So, you might start **mitmdump** as follows: ->>> mitmdump --replace-from-file :~q:foo:~/xss-exploit +>>> mitmdump --replacements :~q:foo:@~/xss-exploit This will load the replacement text from the file ``~/xss-exploit``. -Both the ``--replace`` and ``--replace-from-file`` flags can be passed multiple +The ``--replacements`` flag can be passed multiple times. @@ -66,7 +67,6 @@ replacement hooks using a built-in editor. The context-sensitive help (:kbd:`?`) complete usage information. ================== ======================= -command-line ``--replace``, - ``--replace-from-file`` +command-line ``--replacements`` mitmproxy shortcut :kbd:`O` then :kbd:`R` ================== ======================= |