vee1e/mitmproxy
1
0
Fork 0
mirror of https://github.com/vee1e/mitmproxy.git synced 2026-09-01 18:27:18 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions

Fixed typo in __init__.py (#6008)

Browse source
This commit is contained in:
ZzZombo 2023-03-24 19:25:36 +08:00 • committed by GitHub
parent 8e7564e995
commit 33a81a0ead
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
1 changed files with 4 additions and 4 deletions
Download patch file Download diff file Expand all files Collapse all files

8
mitmproxy/proxy/__init__.py
View file

@ -6,12 +6,12 @@ The most important primitives are:
- Layers: represent protocol layers, e.g. one for TCP, TLS, and so on. Layers are nested, so
a typical configuration might be ReverseProxy/TLS/TCP.
Most importantly, layers are implemented using the sans-io pattern (https://sans-io.readthedocs.io/).
This means that calls return immediately, their is no blocking sync or async code.
- Server: the proxy server handles all I/O. This is implemented using asyncio, but could be done any other way.
The ConnectionHandler is subclassed in the Proxyserver addon, which handles the communication with the
This means that calls return immediately, there is no blocking sync or async code.
- Server: the proxy server handles all I/O. This is implemented using `asyncio`, but could be done any other way.
The `ConnectionHandler` is subclassed in the `Proxyserver` addon, which handles the communication with the
rest of mitmproxy.
- Events: When I/O actions occur at the proxy server, they are passed to the outermost layer as events,
e.g. "DataReceived" or "ConnectionClosed".
e.g. `DataReceived` or `ConnectionClosed`.
- Commands: In the other direction, layers can emit commands to higher layers or the proxy server.
This is used to e.g. send data, request for new connections to be opened, or to call mitmproxy's
event hooks.