diff options
| author | srdusr <[email protected]> | 2026-08-30 12:32:00 +0200 |
|---|---|---|
| committer | srdusr <[email protected]> | 2026-08-30 12:32:00 +0200 |
| commit | da85b510dd7683165f0d31c18a838ca2aea43f60 (patch) | |
| tree | 983e43dc0ecb6b471ee35c638560deeac51a8dab /README.md | |
| parent | 2ee4a95c9ccc701482c88f58840568738354dc36 (diff) | |
| download | mitmux-da85b510dd7683165f0d31c18a838ca2aea43f60.tar.gz mitmux-da85b510dd7683165f0d31c18a838ca2aea43f60.zip | |
Diffstat (limited to 'README.md')
| -rw-r--r-- | README.md | 2 |
1 files changed, 1 insertions, 1 deletions
@@ -577,7 +577,7 @@ engine, and the TUI restarting (or crashing) never interrupts capture. Capture fidelity is the other core design constraint: for HTTP/1.1 traffic, request and response bytes stored in history are exactly what was read off the wire - captured via a `net.Conn` wrapper that records -bytes as `net/http`'s own (memory-safe, battle-tested) parser consumes +bytes as `net/http`'s own (memory-safe) parser consumes them, rather than re-serializing a parsed representation. For HTTP/2, which has no meaningful single "raw bytes" form, the stored representation is a reconstruction, and every stored entry says which |