Replies: 1 comment 2 replies
-
My understanding is that FWIW, one workaround for this problem is to use https://docs.mitmproxy.org/dev/concepts-options/#stream_large_bodies. |
Beta Was this translation helpful? Give feedback.
2 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
What bought this to my attention was with my personal experience loading flow files. I had saved api requests for a video game download, which means the response data was abnormally large (GBs of data...). I noticed mitm seems to load the entire file into memory before parsing it. I understand most use-cases are not mine, but this isn't optimal.
I looked at the source and also noticed mitm uses tnetstrings for storing data, is there any reason to use this over the built-in struct module?
And tying both of these together, the
io.tnetstrings
module seems to only read/writeFlow
objects but currently reads an entire tnetstring while staying unaware of the underlying data structure. If concrete methods were written forio.tnetstring
, readingFlow
objects could be optimized to ignore certain fields.I would be willing to make contributions here.
Beta Was this translation helpful? Give feedback.
All reactions