Release mitmproxy 0.2
This commit is contained in:
parent
f457342aab
commit
e98a035540
|
@ -0,0 +1,24 @@
|
|||
|
||||
|
||||
1 March 2010: mitmproxy 0.2
|
||||
|
||||
* Big speed and responsiveness improvements, thanks to Thomas Roth
|
||||
|
||||
* Support urwid 0.9.9
|
||||
*
|
||||
* Terminal beeping based on filter expressions
|
||||
|
||||
* Filter expressions for terminal beeps, limits, interceptions and sticky
|
||||
cookies can now be passed on the command line.
|
||||
|
||||
* Save requests and responses to file
|
||||
|
||||
* Split off non-interactive dump functionality into a new tool called
|
||||
mitmdump
|
||||
|
||||
* "A" will now accept all intercepted connections
|
||||
|
||||
* Lots of bugfixes
|
||||
|
||||
|
||||
|
8
README
8
README
|
@ -4,10 +4,10 @@ underlying library that mitmproxy is built on can also be used to do these
|
|||
things programmatically.
|
||||
|
||||
By default, mitmproxy starts up with a mutt-like interactive curses interface -
|
||||
the help page (which you can view by pressing "?") should tell you everything
|
||||
you need to know. Note that requests and responses are stored in-memory until
|
||||
you delete them, so leaving mitmproxy running indefinitely or requesting very
|
||||
large amounts of data through it is a bad idea.
|
||||
the built-in help page (which you can view by pressing "?") will tell you
|
||||
everything you need to know. Note that requests and responses are stored
|
||||
in-memory until you delete them, so leaving mitmproxy running indefinitely or
|
||||
requesting very large amounts of data through it is a bad idea.
|
||||
|
||||
SSL
|
||||
---
|
||||
|
|
Loading…
Reference in New Issue