mirror of
https://github.com/Grasscutters/mitmproxy.git
synced 2024-11-27 02:24:18 +00:00
40 lines
1.6 KiB
Python
40 lines
1.6 KiB
Python
"""
|
|
In mitmproxy, protocols are implemented as a set of layers, which are composed on top each other.
|
|
The first layer is usually the proxy mode, e.g. transparent proxy or normal HTTP proxy. Next,
|
|
various protocol layers are stacked on top of each other - imagine WebSockets on top of an HTTP
|
|
Upgrade request. An actual mitmproxy connection may look as follows (outermost layer first):
|
|
|
|
Transparent HTTP proxy, no TLS:
|
|
- TransparentProxy
|
|
- Http1Layer
|
|
- HttpLayer
|
|
|
|
Regular proxy, CONNECT request with WebSockets over SSL:
|
|
- ReverseProxy
|
|
- Http1Layer
|
|
- HttpLayer
|
|
- TLSLayer
|
|
- WebsocketLayer (or TCPLayer)
|
|
|
|
Every layer acts as a read-only context for its inner layers (see :py:class:`Layer`). To communicate
|
|
with an outer layer, a layer can use functions provided in the context. The next layer is always
|
|
determined by a call to :py:meth:`.next_layer() <libmproxy.proxy.RootContext.next_layer>`,
|
|
which is provided by the root context.
|
|
|
|
Another subtle design goal of this architecture is that upstream connections should be established
|
|
as late as possible; this makes server replay without any outgoing connections possible.
|
|
"""
|
|
|
|
from __future__ import (absolute_import, print_function, division)
|
|
from .base import Layer, ServerConnectionMixin, Kill
|
|
from .http import Http1Layer, UpstreamConnectLayer, Http2Layer
|
|
from .tls import TlsLayer, is_tls_record_magic
|
|
from .rawtcp import RawTCPLayer
|
|
|
|
__all__ = [
|
|
"Layer", "ServerConnectionMixin", "Kill",
|
|
"Http1Layer", "UpstreamConnectLayer", "Http2Layer",
|
|
"TlsLayer", "is_tls_record_magic",
|
|
"RawTCPLayer"
|
|
]
|