mitmproxy/pathod/protocols
Aldo Cortesi 978b8d095c mitmproxy.types -> mitmproxy.coretypes
The types name is valuable, and we have a better use for it in collecting and
exposing types for options and commands.

The coretypes module should probably be split up anyway - it contains a
threading base class, a few container objects, and the defintion of our
serialization protocol. I was tempted to rename it to "uncagegorized" for the
sake of honesty.
2017-12-17 13:31:36 +13:00
..
__init__.py
http.py
http2.py mitmproxy.types -> mitmproxy.coretypes 2017-12-17 13:31:36 +13:00
websockets.py