mirror of
https://github.com/Grasscutters/mitmproxy.git
synced 2024-11-23 00:01:36 +00:00
104 lines
3.6 KiB
ReStructuredText
104 lines
3.6 KiB
ReStructuredText
.. _streaming:
|
|
|
|
HTTP Streaming
|
|
==============
|
|
|
|
By default, mitmproxy will read the entire request/response, perform any indicated
|
|
manipulations on it and then send the (possibly modified) request or response to
|
|
the server or the client respectively. In some cases this is undesirable and you may wish to "stream"
|
|
the request/response. When streaming is enabled, the request/response is
|
|
not buffered on the proxy but directly sent to the server/client instead.
|
|
Though, HTTP headers are still fully buffered before being sent.
|
|
|
|
Response Streaming
|
|
------------------
|
|
|
|
By using mitmproxy's streaming feature, response contents can be passed to the client incrementally
|
|
before they have been fully received by the proxy. This is especially useful for large binary files
|
|
such as videos, where buffering the whole file slows down the client's browser.
|
|
|
|
Request Streaming
|
|
-----------------
|
|
|
|
As the name suggests, request streaming feature can be used to stream request body to the server incrementally
|
|
before it has been fully received by the proxy. This may be useful for large file uploads.
|
|
|
|
|
|
On the command-line
|
|
-------------------
|
|
|
|
Streaming can be enabled on the command line for all request and response bodies exceeding a certain size.
|
|
The SIZE argument understands k/m/g suffixes, e.g. 3m for 3 megabytes.
|
|
|
|
================== =================
|
|
command-line ``--set stream_large_bodies=SIZE``
|
|
================== =================
|
|
|
|
.. warning::
|
|
|
|
When streaming is enabled, **streamed request/response contents will not be
|
|
recorded or preserved in any way.**
|
|
|
|
.. note::
|
|
|
|
When streaming is enabled, the request/response body cannot be modified by the usual means.
|
|
|
|
Customizing Streaming
|
|
---------------------
|
|
|
|
You can also use a script to customize exactly which requests or responses are streamed.
|
|
|
|
Requests/Responses that should be tagged for streaming by setting their ``.stream``
|
|
attribute to ``True``:
|
|
|
|
.. literalinclude:: ../../examples/complex/stream.py
|
|
:caption: examples/complex/stream.py
|
|
:language: python
|
|
|
|
Implementation Details
|
|
----------------------
|
|
|
|
When response streaming is enabled, portions of the code which would have otherwise performed
|
|
changes on the request/response body will see an empty body. Any modifications will be ignored.
|
|
|
|
Streamed bodies are usually sent in chunks of 4096 bytes. If the response is sent with a
|
|
``Transfer-Encoding: chunked`` header, the response will be streamed one chunk at a time.
|
|
|
|
Modifying streamed data
|
|
-----------------------
|
|
|
|
If the ``.stream`` attribute is callable, ``.stream`` will wrap the generator that yields all
|
|
chunks.
|
|
|
|
.. literalinclude:: ../../examples/complex/stream_modify.py
|
|
:caption: examples/complex/stream_modify.py
|
|
:language: python
|
|
|
|
WebSocket Streaming
|
|
===================
|
|
|
|
The WebSocket streaming feature can be used to send the frames as soon as they arrive. This can be useful for large binary file transfers.
|
|
|
|
On the command-line
|
|
-------------------
|
|
|
|
Streaming can be enabled on the command line for all WebSocket frames
|
|
|
|
================== =================
|
|
command-line ``--set stream_websockets=true``
|
|
================== =================
|
|
|
|
.. note::
|
|
|
|
When Web Socket streaming is enabled, the message payload cannot be modified.
|
|
|
|
Implementation Details
|
|
----------------------
|
|
When WebSocket streaming is enabled, portions of the code which may perform changes to the WebSocket message payloads will not have
|
|
any effect on the actual payload sent to the server as the frames are sent as and when the arrive.
|
|
Though the message payload will be stored in the WebSocket Flow unlike request/response streaming where the body is not stored.
|
|
|
|
.. seealso::
|
|
|
|
- :ref:`passthrough`
|