2015-09-06 01:20:58 +00:00
|
|
|
.. _tcpproxy:
|
|
|
|
|
|
|
|
|
|
TCP Proxy
|
|
|
|
|
=========
|
|
|
|
|
|
|
|
|
|
WebSockets or other non-HTTP protocols are not supported by mitmproxy yet. However, you can exempt
|
|
|
|
|
hostnames from processing, so that mitmproxy acts as a generic TCP forwarder.
|
|
|
|
|
This feature is closely related to the :ref:`passthrough` functionality,
|
|
|
|
|
but differs in two important aspects:
|
|
|
|
|
|
|
|
|
|
- The raw TCP messages are printed to the event log.
|
|
|
|
|
- SSL connections will be intercepted.
|
|
|
|
|
|
|
|
|
|
Please note that message interception or modification are not possible yet.
|
|
|
|
|
If you are not interested in the raw TCP messages, you should use the ignore domains feature.
|
|
|
|
|
|
|
|
|
|
How it works
|
|
|
|
|
------------
|
|
|
|
|
|
|
|
|
|
================== ======================
|
2016-06-07 02:08:46 +00:00
|
|
|
command-line ``--tcp HOST``
|
2015-09-06 01:20:58 +00:00
|
|
|
mitmproxy shortcut :kbd:`o` then :kbd:`T`
|
|
|
|
|
================== ======================
|
|
|
|
|
|
2015-09-07 08:52:18 +00:00
|
|
|
For a detailed description how the hostname pattern works, please look at the :ref:`passthrough`
|
|
|
|
|
feature.
|
2015-09-06 01:20:58 +00:00
|
|
|
|
|
|
|
|
.. seealso::
|
|
|
|
|
|
|
|
|
|
- :ref:`passthrough`
|
|
|
|
|
- :ref:`responsestreaming`
|
