![]() ![]() New tls_ event hooks to record negotiation success/failure #4790)ĬVE-2022-24766: Fix request smuggling vulnerability reported by Changelog Major improvements to the web interface hooks can now be async #5106) ![]() (#5339, handling of multiple Cookie headers when proxying HTTP/2 to HTTP/1 (#5337, March 2022: mitmproxy 8.0.0 (#5332, performance and memory usage by reusing OpenSSL contexts. (#5319, HTTP/2 information responses instead of raising an error. (#5297, hostname encoding for IDNA domains in upstream mode. This preempts the upcoming deprecation of Python's mailcap module. (#5278, opening an external viewer for message contents, mailcap files are not considered anymore. (#5264, example script for manipulating cookies. (#5217, cut addon to better handle binary contents (#3965, text truncation for full-width characters (#4278, mitmweb export copy failed in non-secure domain. (#5225, example addon for domain fronting. (#4469, flatpak support to the browser addon (#5200, example addon to dump contents to files based on a filter expression (#5190, a bug where the wrong SNI is sent to an upstream HTTPS proxy (#5109, sure that mitmproxy displays error messages on startup. ![]() (#5046, Performance Improvements (#3427, users if server side event responses are received without streaming. (#5227, send HTTP/2 ping frames to keep connections alive. (#4786, flows retain their current position in the flow list. (#5233, a memory leak in mitmdump where flows were kept in memory. (#5428, overambitious assertions in the HTTP state machine, fix some error handling. (#5401, huge (>65kb) http2 responses corrupted. Support specifying the local address for outgoing connections (#5364, a bug where an excess empty chunk has been sent for chunked HEAD request. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |