From 3353aa3cfdde33e7f7465739f2cf65bfd4697c24 Mon Sep 17 00:00:00 2001 From: Thomas Kriechbaumer Date: Mon, 21 Nov 2016 22:54:47 +0100 Subject: fix docs --- docs/features/tcpproxy.rst | 2 +- docs/scripting/events.rst | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/features/tcpproxy.rst b/docs/features/tcpproxy.rst index e24620e2..77c62bbf 100644 --- a/docs/features/tcpproxy.rst +++ b/docs/features/tcpproxy.rst @@ -3,7 +3,7 @@ TCP Proxy ========= -Non-HTTP protocols are not supported by mitmproxy yet. However, you can exempt +In case mitmproxy does not handle a specific protocol, 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: diff --git a/docs/scripting/events.rst b/docs/scripting/events.rst index a0fc1243..8f9463ff 100644 --- a/docs/scripting/events.rst +++ b/docs/scripting/events.rst @@ -168,7 +168,7 @@ are issued, only new WebSocket messages are called. * - .. py:function:: websocket_handshake(flow) - Called when a client wants to establish a WebSocket connection. The - WebSocket-specific headers can be manipulated to manipulate the + WebSocket-specific headers can be manipulated to alter the handshake. The ``flow`` object is guaranteed to have a non-None ``request`` attribute. -- cgit v1.2.3