2017-08-17 08:18:05 +00:00
|
|
|
.. _websocket_protocol:
|
|
|
|
|
|
|
|
|
|
WebSocket
|
|
|
|
|
=========
|
|
|
|
|
|
|
|
|
|
.. seealso::
|
|
|
|
|
|
|
|
|
|
- `RFC6455: The WebSocket Protocol <http://tools.ietf.org/html/rfc6455>`_
|
|
|
|
|
- `RFC7692: Compression Extensions for WebSocket <http://tools.ietf.org/html/rfc7692>`_
|
|
|
|
|
|
|
|
|
|
WebSocket support in mitmproxy is based on the amazing work by the python-hyper
|
|
|
|
|
community with the `wsproto <https://github.com/python-hyper/wsproto>`_
|
|
|
|
|
project. It fully encapsulates WebSocket frames/messages/connections and
|
|
|
|
|
provides an easy-to-use event-based API.
|
|
|
|
|
|
|
|
|
|
mitmproxy fully supports the compression extension for WebSocket messages,
|
|
|
|
|
provided by wsproto.
|
2017-08-17 08:38:02 +00:00
|
|
|
|
|
|
|
|
If an endpoint sends a PING to mitmproxy, a PONG will be sent back immediately
|
|
|
|
|
(with the same payload if present). To keep the other connection alive, a new
|
|
|
|
|
PING (without a payload) is sent to the other endpoint. Unsolicited PONG's are
|
|
|
|
|
not forwarded. All PING's and PONG's are logged (with payload if present).
|
