All new documentation
This patch does a lot.
- Ditch sphinx in favor of hugo. This gives us complete control of the layout
and presentation of our docs. Henceforth, docs will be hosted on our website
rather than ReadTheDocs.
- Create a simple, clean doc layout and theme.
- Remove large parts of the documentaion. I've ditched anything that was a)
woefully out of date, b) too detailed, or c) too hard to maintain in the long
term.
- Huge updates to the docs themselves: completely rewrite addons documentation,
add docs for core concepts like commands and options, and revise and tweak a
lot of the existing docs.
With this patch, we're also changing the way we publish and maintain the docs.
From now on, we don't publish docs for every release. Instead, the website will
contain ONE set of docs for each major release. The online docs will be updated
if needed as minor releases are made. Docs are free to improve during minor
releases, but anything that changes behaviour sufficiently to require a doc
change warrants a new major release. This also leaves us free to progressively
update and improve docs out of step with our release cadence.
With this new scheme, I feel CI over the docs is less important. I've removed
it for now, but won't object if someone wants to add it back in.
2018-02-22 04:21:34 +00:00
|
|
|
import typing
|
|
|
|
|
|
|
|
import mitmproxy.addonmanager
|
|
|
|
import mitmproxy.connections
|
|
|
|
import mitmproxy.http
|
|
|
|
import mitmproxy.log
|
|
|
|
import mitmproxy.tcp
|
|
|
|
import mitmproxy.websocket
|
|
|
|
import mitmproxy.proxy.protocol
|
|
|
|
|
|
|
|
|
|
|
|
class Events:
|
|
|
|
# HTTP lifecycle
|
|
|
|
def http_connect(self, flow: mitmproxy.http.HTTPFlow):
|
|
|
|
"""
|
|
|
|
An HTTP CONNECT request was received. Setting a non 2xx response on
|
|
|
|
the flow will return the response to the client abort the
|
|
|
|
connection. CONNECT requests and responses do not generate the usual
|
|
|
|
HTTP handler events. CONNECT requests are only valid in regular and
|
|
|
|
upstream proxy modes.
|
|
|
|
"""
|
|
|
|
|
|
|
|
def requestheaders(self, flow: mitmproxy.http.HTTPFlow):
|
|
|
|
"""
|
|
|
|
HTTP request headers were successfully read. At this point, the body
|
|
|
|
is empty.
|
|
|
|
"""
|
|
|
|
|
|
|
|
def request(self, flow: mitmproxy.http.HTTPFlow):
|
|
|
|
"""
|
|
|
|
The full HTTP request has been read.
|
|
|
|
"""
|
|
|
|
|
|
|
|
def responseheaders(self, flow: mitmproxy.http.HTTPFlow):
|
|
|
|
"""
|
|
|
|
HTTP response headers were successfully read. At this point, the body
|
|
|
|
is empty.
|
|
|
|
"""
|
|
|
|
|
|
|
|
def response(self, flow: mitmproxy.http.HTTPFlow):
|
|
|
|
"""
|
|
|
|
The full HTTP response has been read.
|
|
|
|
"""
|
|
|
|
|
|
|
|
def error(self, flow: mitmproxy.http.HTTPFlow):
|
|
|
|
"""
|
|
|
|
An HTTP error has occurred, e.g. invalid server responses, or
|
|
|
|
interrupted connections. This is distinct from a valid server HTTP
|
|
|
|
error response, which is simply a response with an HTTP error code.
|
|
|
|
"""
|
|
|
|
|
|
|
|
# TCP lifecycle
|
|
|
|
def tcp_start(self, flow: mitmproxy.tcp.TCPFlow):
|
|
|
|
"""
|
|
|
|
A TCP connection has started.
|
|
|
|
"""
|
|
|
|
|
|
|
|
def tcp_message(self, flow: mitmproxy.tcp.TCPFlow):
|
|
|
|
"""
|
|
|
|
A TCP connection has received a message. The most recent message
|
|
|
|
will be flow.messages[-1]. The message is user-modifiable.
|
|
|
|
"""
|
|
|
|
|
|
|
|
def tcp_error(self, flow: mitmproxy.tcp.TCPFlow):
|
|
|
|
"""
|
|
|
|
A TCP error has occurred.
|
|
|
|
"""
|
|
|
|
|
|
|
|
def tcp_end(self, flow: mitmproxy.tcp.TCPFlow):
|
|
|
|
"""
|
|
|
|
A TCP connection has ended.
|
|
|
|
"""
|
|
|
|
|
|
|
|
# Websocket lifecycle
|
|
|
|
def websocket_handshake(self, flow: mitmproxy.http.HTTPFlow):
|
|
|
|
"""
|
|
|
|
Called when a client wants to establish a WebSocket connection. The
|
|
|
|
WebSocket-specific headers can be manipulated to alter the
|
|
|
|
handshake. The flow object is guaranteed to have a non-None request
|
|
|
|
attribute.
|
|
|
|
"""
|
|
|
|
|
|
|
|
def websocket_start(self, flow: mitmproxy.websocket.WebsocketFlow):
|
|
|
|
"""
|
|
|
|
A websocket connection has commenced.
|
|
|
|
"""
|
|
|
|
|
|
|
|
def websocket_message(self, flow: mitmproxy.websocket.WebsocketFlow):
|
|
|
|
"""
|
|
|
|
Called when a WebSocket message is received from the client or
|
|
|
|
server. The most recent message will be flow.messages[-1]. The
|
|
|
|
message is user-modifiable. Currently there are two types of
|
|
|
|
messages, corresponding to the BINARY and TEXT frame types.
|
|
|
|
"""
|
|
|
|
|
|
|
|
def websocket_error(self, flow: mitmproxy.websocket.WebsocketFlow):
|
|
|
|
"""
|
|
|
|
A websocket connection has had an error.
|
|
|
|
"""
|
|
|
|
|
|
|
|
def websocket_end(self, flow: mitmproxy.websocket.WebsocketFlow):
|
|
|
|
"""
|
|
|
|
A websocket connection has ended.
|
|
|
|
"""
|
|
|
|
|
|
|
|
# Network lifecycle
|
|
|
|
def clientconnect(self, layer: mitmproxy.proxy.protocol.Layer):
|
|
|
|
"""
|
|
|
|
A client has connected to mitmproxy. Note that a connection can
|
|
|
|
correspond to multiple HTTP requests.
|
|
|
|
"""
|
|
|
|
|
|
|
|
def clientdisconnect(self, layer: mitmproxy.proxy.protocol.Layer):
|
|
|
|
"""
|
|
|
|
A client has disconnected from mitmproxy.
|
|
|
|
"""
|
|
|
|
|
|
|
|
def serverconnect(self, conn: mitmproxy.connections.ServerConnection):
|
|
|
|
"""
|
|
|
|
Mitmproxy has connected to a server. Note that a connection can
|
|
|
|
correspond to multiple requests.
|
|
|
|
"""
|
|
|
|
|
|
|
|
def serverdisconnect(self, conn: mitmproxy.connections.ServerConnection):
|
|
|
|
"""
|
|
|
|
Mitmproxy has disconnected from a server.
|
|
|
|
"""
|
|
|
|
|
|
|
|
def next_layer(self, layer: mitmproxy.proxy.protocol.Layer):
|
|
|
|
"""
|
|
|
|
Network layers are being switched. You may change which layer will
|
|
|
|
be used by returning a new layer object from this event.
|
|
|
|
"""
|
|
|
|
|
|
|
|
# General lifecycle
|
|
|
|
def configure(self, updated: typing.Set[str]):
|
|
|
|
"""
|
|
|
|
Called when configuration changes. The updated argument is a
|
|
|
|
set-like object containing the keys of all changed options. This
|
|
|
|
event is called during startup with all options in the updated set.
|
|
|
|
"""
|
|
|
|
|
|
|
|
def done(self):
|
|
|
|
"""
|
|
|
|
Called when the addon shuts down, either by being removed from the
|
|
|
|
mitmproxy instance, or when mitmproxy itself shuts down.
|
|
|
|
"""
|
|
|
|
|
|
|
|
def load(self, entry: mitmproxy.addonmanager.Loader):
|
|
|
|
"""
|
|
|
|
Called when an addon is first loaded. This event receives a Loader
|
|
|
|
object, which contains methods for adding options and commands. This
|
|
|
|
method is where the addon configures itself.
|
|
|
|
"""
|
|
|
|
|
|
|
|
def log(self, entry: mitmproxy.log.LogEntry):
|
|
|
|
"""
|
2018-02-25 02:45:11 +00:00
|
|
|
Called whenever a new log entry is created through the mitmproxy
|
All new documentation
This patch does a lot.
- Ditch sphinx in favor of hugo. This gives us complete control of the layout
and presentation of our docs. Henceforth, docs will be hosted on our website
rather than ReadTheDocs.
- Create a simple, clean doc layout and theme.
- Remove large parts of the documentaion. I've ditched anything that was a)
woefully out of date, b) too detailed, or c) too hard to maintain in the long
term.
- Huge updates to the docs themselves: completely rewrite addons documentation,
add docs for core concepts like commands and options, and revise and tweak a
lot of the existing docs.
With this patch, we're also changing the way we publish and maintain the docs.
From now on, we don't publish docs for every release. Instead, the website will
contain ONE set of docs for each major release. The online docs will be updated
if needed as minor releases are made. Docs are free to improve during minor
releases, but anything that changes behaviour sufficiently to require a doc
change warrants a new major release. This also leaves us free to progressively
update and improve docs out of step with our release cadence.
With this new scheme, I feel CI over the docs is less important. I've removed
it for now, but won't object if someone wants to add it back in.
2018-02-22 04:21:34 +00:00
|
|
|
context. Be careful not to log from this event, which will cause an
|
|
|
|
infinite loop!
|
|
|
|
"""
|
|
|
|
|
|
|
|
def running(self):
|
|
|
|
"""
|
|
|
|
Called when the proxy is completely up and running. At this point,
|
|
|
|
you can expect the proxy to be bound to a port, and all addons to be
|
|
|
|
loaded.
|
|
|
|
"""
|
|
|
|
|
|
|
|
def tick(self):
|
|
|
|
"""
|
|
|
|
A regular ticker - called approximately once every 100ms.
|
|
|
|
"""
|
|
|
|
|
|
|
|
def update(self, flows: typing.Sequence[mitmproxy.flow.Flow]):
|
|
|
|
"""
|
|
|
|
Update is called when one or more flow objects have been modified,
|
|
|
|
usually from a different addon.
|
|
|
|
"""
|