diff options
| author | Aldo Cortesi <aldo@nullcube.com> | 2010-03-01 17:25:27 +1300 |
|---|---|---|
| committer | Aldo Cortesi <aldo@nullcube.com> | 2010-03-01 17:25:27 +1300 |
| commit | e98a035540559c766dddaff44b7327ab828f3672 (patch) | |
| tree | d6aa36a2575c0e33b942bb2a6163f2dce7f221d5 /README | |
| parent | f457342aab854d4cb34f918ba07b24168df9269c (diff) | |
| download | mitmproxy-e98a035540559c766dddaff44b7327ab828f3672.tar.gz mitmproxy-e98a035540559c766dddaff44b7327ab828f3672.tar.bz2 mitmproxy-e98a035540559c766dddaff44b7327ab828f3672.zip | |
Release mitmproxy 0.2
Diffstat (limited to 'README')
| -rw-r--r-- | README | 8 |
1 files changed, 4 insertions, 4 deletions
@@ -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 --- |