Grasscutters/mitmproxy
3
0
Fork 0
mirror of https://github.com/Grasscutters/mitmproxy.git synced 2024-11-26 02:10:59 +00:00
Code Issues Projects Releases Wiki Activity

fix docs

Browse Source
This commit is contained in:
Thomas Kriechbaumer 2016-11-21 22:54:47 +01:00
parent d3bd04dec0
commit 3353aa3cfd
2 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
docs/features/tcpproxy.rst
View File

@ -3,7 +3,7 @@
TCP Proxy 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. hostnames from processing, so that mitmproxy acts as a generic TCP forwarder.
This feature is closely related to the :ref:`passthrough` functionality, This feature is closely related to the :ref:`passthrough` functionality,
but differs in two important aspects: but differs in two important aspects:

2
docs/scripting/events.rst
View File

@ -168,7 +168,7 @@ are issued, only new WebSocket messages are called.
* - .. py:function:: websocket_handshake(flow) * - .. py:function:: websocket_handshake(flow)
- Called when a client wants to establish a WebSocket connection. The - 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 handshake. The ``flow`` object is guaranteed to have a non-None
``request`` attribute. ``request`` attribute.